public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: w@1wt.eu
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	Mikael Pettersson <mikpe@it.uu.se>,
	David Miller <davem@davemloft.net>
Subject: Re: Linux 2.4.34-pre3
Date: Wed, 20 Sep 2006 03:42:06 +1000	[thread overview]
Message-ID: <45102BEE.9000501@yahoo.com.au> (raw)
In-Reply-To: <20060919173253.GA25470@hera.kernel.org>

Willy Tarreau wrote:
> Hello !
> 
> I've been a little bit silent and quite busy too. As announced with -pre2,
> here comes -pre3 with only GCC4 fixes. Other fixes I received are minor
> and can wait for -pre4. I really want people to test -pre3 without adding
> any noise to the test. There should be *no* regression at all with existing
> compilers.
> 
> Gcc 4.1 is known to build x86, x86_64, ppc, sparc64, and sparc. Only sparc
> has received no testing yet, while sparc64 is OK. It is possible that some
> sparc/sparc64 drivers have not been caught because of undetected options
> combinations (Davem CC'd for any possible advice on this mater). Status
> for other archs is unknown but at least must not be affected for existing
> setups.
> 
> You will notice that most of the changes below appear under my name while
> I do not deserve any credit for the changes. It is just because I've cut
> all the fixes to sort them, and committed them myself individually. But
> the real work has been done by Mikael.
> 
> We have worked *very* carefully on this merge, and we hope to get all
> possible feedback. People who encounter build problems on archs listed
> above are free to report them, possibly with the fix. When providing a
> fix, *please* provide the whole error output in the commit message so
> that we can track what has been fixed. People who want to include support
> for other archs will have to provide patches, as (at least for me) we
> are not equipped to build on other archs (except for alpha when my RAM
> arrives).
> 
> I plan to wait up to the end of this month before providing -pre4 if there
> is no feedback. Important fixes will be subject to another -stable release
> anyway, so it's safe to wait for feedback here.

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.

-- 
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com 

  reply	other threads:[~2006-09-19 17:42 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 [this message]
2006-09-19 18:17   ` Willy Tarreau
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=45102BEE.9000501@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@it.uu.se \
    --cc=mtosatti@redhat.com \
    --cc=w@1wt.eu \
    /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