From: Andrea Arcangeli <andrea@suse.de>
To: Rik van Riel <riel@redhat.com>
Cc: Hugh Dickins <hugh@veritas.com>,
Matt_Domsch@Dell.com, marcelo.tosatti@cyclades.com,
linux-kernel@vger.kernel.org, benh@kernel.crashing.org
Subject: Re: [PATCH] page->flags corruption fix
Date: Sun, 12 Oct 2003 16:36:17 +0200 [thread overview]
Message-ID: <20031012143617.GS16013@velociraptor.random> (raw)
In-Reply-To: <Pine.LNX.4.44.0310121009560.30191-100000@cluless.boston.redhat.com>
On Sun, Oct 12, 2003 at 10:11:43AM -0400, Rik van Riel wrote:
> On Sun, 12 Oct 2003, Hugh Dickins wrote:
>
> > I agree on that too: I think Rik did it for atomicity throughout,
> > to make the safety obvious; but in practice it was already safe.
>
> Also to keep this fix future proof. Who knows whether
> a super-optimised patch that masks just this particular
> race condition will still be safe when XFS is merged ?
>
> I really don't like keeping the code fragile and making
> it easy to reintroduce bugs.
free_pages as said if it's buggy, then it can still trigger no matter
whatever you do there, at that deep point of free_pages a alloc_page
user will be able to get the page and corrupt it anyways, so it can't
help and it will never be able to help no matter what xfs or whatever
else gets merged. If that makes a difference alloc_page users will still
break it.
we can argue about the filemap.c part, but I'm sure the page_alloc.c part
can't make any sense ever.
Andrea - If you prefer relying on open source software, check these links:
rsync.kernel.org::pub/scm/linux/kernel/bkcvs/linux-2.[45]/
http://www.cobite.com/cvsps/
next prev parent reply other threads:[~2003-10-12 14:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-08 15:31 [PATCH] page->flags corruption fix Matt_Domsch
2003-10-08 15:53 ` Hugh Dickins
2003-10-08 15:59 ` Rik van Riel
2003-10-08 17:15 ` Hugh Dickins
2003-10-08 17:41 ` Marcelo Tosatti
2003-10-08 17:52 ` Rik van Riel
2003-10-11 13:48 ` Andrea Arcangeli
2003-10-11 16:03 ` Andrea Arcangeli
2003-10-12 11:15 ` Hugh Dickins
2003-10-12 13:21 ` Andrea Arcangeli
2003-10-12 13:35 ` Andrea Arcangeli
2003-10-12 14:11 ` Rik van Riel
2003-10-12 14:36 ` Andrea Arcangeli [this message]
2003-10-12 17:20 ` Rik van Riel
2003-10-12 20:40 ` Andrea Arcangeli
-- strict thread matches above, loose matches on Subject: below --
2003-10-07 16:26 Rik van Riel
2003-10-08 14:49 ` Hugh Dickins
2003-10-08 14:57 ` David S. Miller
2003-10-08 15:10 ` Rik van Riel
2003-10-08 15:47 ` Hugh Dickins
2003-10-08 15:52 ` Rik van Riel
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=20031012143617.GS16013@velociraptor.random \
--to=andrea@suse.de \
--cc=Matt_Domsch@Dell.com \
--cc=benh@kernel.crashing.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=riel@redhat.com \
/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