From: Robert Love <rml@tech9.net>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Alexander Viro <viro@math.psu.edu>,
Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.5: push BKL out of llseek
Date: 30 Jan 2002 08:39:12 -0500 [thread overview]
Message-ID: <1012397957.3219.27.camel@phantasy> (raw)
In-Reply-To: <shs3d0oi7zp.fsf@charged.uio.no>
In-Reply-To: <Pine.GSO.4.21.0201292349260.11157-100000@weyl.math.psu.edu> <shs3d0oi7zp.fsf@charged.uio.no>
On Wed, 2002-01-30 at 03:00, Trond Myklebust wrote:
>> " " == Alexander Viro <viro@math.psu.edu> writes:
>
> > So I'd prefer to do it in two stages - shift BKL into
> > ->llseek() and then see where it can be dropped/replaced with
> > ->i_sem.
>
> Seconded. There are several filesystems out there for which i_sem does
> nothing to protect inode->i_size.
Then the first patch is the way to go. We know generic_file_llseek is
safe and perhaps a few other of the llseek methods. The remaining can
explicitly grab the bkl on their own, as Al suggested.
Robert Love
next prev parent reply other threads:[~2002-01-30 13:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-30 0:00 [PATCH] 2.5: push BKL out of llseek Robert Love
2002-01-30 0:09 ` Linus Torvalds
2002-01-30 0:41 ` Robert Love
2002-01-30 0:52 ` Linus Torvalds
2002-01-30 2:24 ` Robert Love
2002-01-30 1:26 ` Andrew Morton
2002-01-30 2:16 ` Linus Torvalds
2002-01-30 2:20 ` Robert Love
2002-01-30 2:20 ` Andrew Morton
2002-01-30 2:21 ` Dave Jones
2002-01-30 2:37 ` Robert Love
2002-01-30 2:50 ` Nigel Gamble
2002-01-30 3:19 ` Andrew Morton
2002-01-30 9:34 ` Nigel Gamble
2002-01-30 10:36 ` Russell King
2002-01-30 4:54 ` Alexander Viro
2002-01-30 8:00 ` Trond Myklebust
2002-01-30 13:39 ` Robert Love [this message]
2002-01-30 4:50 ` Anton Blanchard
2002-01-30 5:03 ` Robert Love
-- strict thread matches above, loose matches on Subject: below --
2002-01-30 21:14 Martin Wirth
2002-01-31 15:39 Martin Wirth
2002-01-31 21:06 ` Nigel Gamble
2002-02-01 19:29 John Hawkes
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=1012397957.3219.27.camel@phantasy \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=trond.myklebust@fys.uio.no \
--cc=viro@math.psu.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.