From: Willy Tarreau <w@1wt.eu>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: Linux 2.4.34-pre3
Date: Tue, 19 Sep 2006 20:17:38 +0200 [thread overview]
Message-ID: <20060919181738.GA3467@1wt.eu> (raw)
In-Reply-To: <45102BEE.9000501@yahoo.com.au>
Hi Nick,
On Wed, Sep 20, 2006 at 03:42:06AM +1000, Nick Piggin wrote:
[cut -pre3 advertisement]
> I wonder if 2.4 doesn't need the memory ordering fix to prevent pagecache
> corruption in reclaim? (http://www.gatago.com/linux/kernel/14682626.html)
>
> What would need to be done is to test page_count before testing PageDirty,
> and putting an smp_rmb between the two.
I've read the thread, and Linus proposed to add an smp_wmb() in
set_page_dirty() too. I see that an smp_rmb() is already present
in shrink_cache() with the adequate comment. set_page_dirty() begins
with a test_and_set_bit() check. I suspect that transposing the fix
for 2.6 to 2.4 would imply to and an smp_wmb() here :
void fastcall set_page_dirty(struct page *page)
{
if (!test_and_set_bit(PG_dirty, &page->flags)) {
struct address_space *mapping = page->mapping;
+ smp_wmb();
if (mapping) {
spin_lock(&pagecache_lock);
mapping = page->mapping;
But I'm really reluctant on this change, as my knowledge here is rather
limited. Also, the fact that the first proposed part of the patch is here
makes me think that it has already been considered OK.
Maybe I'm wrong, I've CC'd Marcelo for any comments.
Cheers,
Willy
next prev parent reply other threads:[~2006-09-19 18:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-19 17:32 Linux 2.4.34-pre3 Willy Tarreau
2006-09-19 17:42 ` Nick Piggin
2006-09-19 18:17 ` Willy Tarreau [this message]
2006-09-19 18:55 ` Nick Piggin
2006-09-19 20:20 ` Willy Tarreau
-- strict thread matches above, loose matches on Subject: below --
2006-09-20 14:51 Mikael Pettersson
2006-09-20 16:41 ` Willy Tarreau
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=20060919181738.GA3467@1wt.eu \
--to=w@1wt.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=nickpiggin@yahoo.com.au \
/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