From: "Mike Frysinger" <vapier.adi@gmail.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"Bryan Wu" <cooloney@kernel.org>,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
willy@debian.org, viro@zeniv.linux.org.uk,
uclinux-dist-devel@blackfin.uclinux.org, richterd@citi.umich.edu
Subject: Re: [LTP/VFS] fcntl SETLEASE fails on ramfs/tmpfs
Date: Tue, 29 Apr 2008 18:01:47 -0400 [thread overview]
Message-ID: <8bd0f97a0804291501i2751d688h933508df2a4587b4@mail.gmail.com> (raw)
In-Reply-To: <20080429214231.GC26468@fieldses.org>
On Tue, Apr 29, 2008 at 5:42 PM, J. Bruce Fields <bfields@fieldses.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
next prev parent reply other threads:[~2008-04-29 22:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 3:42 Bryan Wu
2008-04-29 20:54 ` Andrew Morton
2008-04-29 21:42 ` J. Bruce Fields
2008-04-29 22:01 ` Mike Frysinger [this message]
2008-04-29 22:11 ` J. Bruce Fields
2008-04-29 22:15 ` Mike Frysinger
2008-04-29 23:21 ` david m. richter
2008-04-30 17:50 ` J. Bruce Fields
2008-04-30 18:14 ` david m. richter
2008-05-01 6:24 ` Al Viro
2008-05-02 22:22 ` J. Bruce Fields
2008-04-29 22:21 ` Matthew Wilcox
2008-05-01 6:33 ` Al Viro
2008-05-02 22:26 ` J. Bruce Fields
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=8bd0f97a0804291501i2751d688h933508df2a4587b4@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bfields@fieldses.org \
--cc=cooloney@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richterd@citi.umich.edu \
--cc=torvalds@linux-foundation.org \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@debian.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®