From: Chris Mason <mason@suse.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: alan@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: generic_file_write change in 2.4.0-ac8
Date: Fri, 12 Jan 2001 16:52:05 -0500 [thread overview]
Message-ID: <23360000.979336325@tiny> (raw)
In-Reply-To: <Pine.GSO.4.21.0101121614150.20629-100000@weyl.math.psu.edu>
On Friday, January 12, 2001 04:30:44 PM -0500 Alexander Viro
<viro@math.psu.edu> wrote:
>
>
> On Fri, 12 Jan 2001, Chris Mason wrote:
>
>>
>> Hi guys,
>>
>> This code for generic_file_write calls vmtruncate without i_sem held. Is
>> that intentional? It should cause problems for reiserfs at least...
>
> Erm... generic_file_write() grabs i_sem upon entry and drops it on exit.
> This call of vmtruncate() is deep inside the protected area.
>
Yup, I'm trying to track down a different problem, and saw what I wanted to
instead of what was really there. Sigh.
-chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-01-12 21:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-12 20:26 generic_file_write change in 2.4.0-ac8 Chris Mason
2001-01-12 21:30 ` Alexander Viro
2001-01-12 21:52 ` Chris Mason [this message]
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=23360000.979336325@tiny \
--to=mason@suse.com \
--cc=alan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox