linux-kernel - Re: [LTP/VFS] fcntl SETLEASE fails on ramfs/tmpfs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <8bd0f97a0804291501i2751d688h933508df2a4587b4@mail.gmail.com>
Date:	Tue, 29 Apr 2008 18:01:47 -0400
From:	"Mike Frysinger" <vapier.adi@...il.com>
To:	"J. Bruce Fields" <bfields@...ldses.org>
Cc:	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Bryan Wu" <cooloney@...nel.org>, linux-kernel@...r.kernel.org,
	torvalds@...ux-foundation.org, willy@...ian.org,
	viro@...iv.linux.org.uk, uclinux-dist-devel@...ckfin.uclinux.org,
	richterd@...i.umich.edu
Subject: Re: [LTP/VFS] fcntl SETLEASE fails on ramfs/tmpfs

On Tue, Apr 29, 2008 at 5:42 PM, J. Bruce Fields <bfields@...ldses.org> wrote:
>  The one thing I suspect is *not* a really serious problem here is the
>  reported LTP failure, since probably the only user of this is Samba,
>  which probably doesn't do a lot of tmpfs exports, and in any case it can
>  probably soldier on (if with degraded performance--how badly I don't
>  know) without getting the write lease it wants.

i'm not sure i follow.  the reported problem is that file locking does
not work on tmpfs/ramfs storage.  a not terribly uncommon scenario is
to use tmpfs on /tmp (or similar location) and have file locking not
work at all.  so programs that use file locking or scripts that
leverage the flock utility from the util-linux package break.
-mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/