ALT Linux Sisyphus discussions
 help / color / mirror / Atom feed
From: "Grigory Batalov" <grisxa@mail.ru>
To: sisyphus@altlinux.org
Subject: [sisyphus] smbfs locking in 2.4.20
Date: Tue, 11 Feb 2003 00:55:49 +0300
Message-ID: <20030211005549.5cb3618f.grisxa@mail.ru> (raw)

 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.


             reply	other threads:[~2003-02-10 21:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-10 21:55 Grigory Batalov [this message]
2003-02-11  8:38 ` AntonFarygin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030211005549.5cb3618f.grisxa@mail.ru \
    --to=grisxa@mail.ru \
    --cc=sisyphus@altlinux.org \
    --cc=sisyphus@altlinux.ru \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

ALT Linux Sisyphus discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/sisyphus/0 sisyphus/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 sisyphus sisyphus/ http://lore.altlinux.org/sisyphus \
		sisyphus@altlinux.ru sisyphus@altlinux.org sisyphus@lists.altlinux.org sisyphus@lists.altlinux.ru sisyphus@lists.altlinux.com sisyphus@linuxteam.iplabs.ru sisyphus@list.linux-os.ru
	public-inbox-index sisyphus

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.sisyphus


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git