From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <grisxa@mail.ru>
Date: Tue, 11 Feb 2003 00:55:49 +0300
From: "Grigory Batalov" <grisxa@mail.ru>
To: sisyphus@altlinux.org
Message-Id: <20030211005549.5cb3618f.grisxa@mail.ru>
Organization: OAO "Kovdorsky GOK"
X-Mailer: Sylpheed version 0.8.0 (GTK+ 1.2.10; i586-alt-linux)
X-Face: ")Qu!$R3ym>`zI`H#Scijb6gliZ{v(u-Y6muu{*\y^\%Chb}{eEo4=L^jB]/>jhI]yW._DV')>_Yj#L`{-(%kaIt76Smg&jk>R>@!QO(p{:dr},@;
Mime-Version: 1.0
Content-Type: text/plain; charset=KOI8-R
Content-Transfer-Encoding: 8bit
Subject: [sisyphus] smbfs locking in 2.4.20
Sender: sisyphus-admin@altlinux.ru
Errors-To: sisyphus-admin@altlinux.ru
X-BeenThere: sisyphus@altlinux.ru
X-Mailman-Version: 2.0.9
Precedence: bulk
Reply-To: sisyphus@altlinux.ru
List-Unsubscribe: <http://altlinux.ru/mailman/listinfo/sisyphus>,
	<mailto:sisyphus-request@altlinux.ru?subject=unsubscribe>
List-Id: <sisyphus.altlinux.ru>
List-Post: <mailto:sisyphus@altlinux.ru>
List-Help: <mailto:sisyphus-request@altlinux.ru?subject=help>
List-Subscribe: <http://altlinux.ru/mailman/listinfo/sisyphus>,
	<mailto:sisyphus-request@altlinux.ru?subject=subscribe>
List-Archive: <http://altlinux.ru/pipermail/sisyphus/>
Archived-At: <http://lore.altlinux.org/sisyphus/20030211005549.5cb3618f.grisxa@mail.ru/>
List-Archive: <http://lore.altlinux.org/sisyphus/>

 Bart Oldeman из Dosemu Team обнаружил, что в ядре 2.4.20
отсутствует блокировка файлов на smbfs. Скорее всего,
он тестировал "чистое" ядро или от Алана Кокса.

 А как обстоят дела в нашем 2.4.20-alt2/altX ?
Если у нас есть walkaround, нельзя ли его присоветовать
коллегам из Dosemu ?


Begin forwarded message:

Date: Mon, 10 Feb 2003 16:28:18 -0500 (EST)
From: Bart Oldeman <oldeman@math.ohio-state.edu>
To: Gregor Ibic <gregor.ibic@intelicom.si>
Subject: WARNING: smbfs and locking (was RE: [PATCH] (locking) (was Re: dosemu and CLIPPER locks (again))))


On Mon, 10 Feb 2003, Gregor Ibic wrote:

> I cant, it is locked. It says resource deadlock avoided.

ok I browsed around a bit and looked at the kernel source, here's the real
answer.

Current (linux kernel 2.4.20) smbfs doesn't support locking at all.

you may look at
http://www.hojdpunkten.ac.se/054/samba
to see some experimental patches though.
NFS *does* support locking though.

So if you see locking "working" with smbfs it is actually by accident and
not by design.

This means that it is very well possible to corrupt your DOS databases
if you access them via smbfs, and there's nothing that DOSEMU can do about
it.

Now, why does a Win client access the file when DOSEMU "locks" it? This is
because there actually is no lock at all!

And the other way around, what happens is that: DOSEMU tries to apply a
lock to the file, the filesystem fails, and the DOS app hence claims that
access is denied.

Bart

-- 
 Grigory Batalov.