linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: "\"J.A. Magallón\"" <jamagallon@ono.com>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>,
	Linus-IDE <linux-ide@vger.kernel.org>
Subject: Re: Linux 2.6.26-rc4
Date: Wed, 28 May 2008 19:59:17 -0400	[thread overview]
Message-ID: <483DF1D5.9030706@tmr.com> (raw)
In-Reply-To: <20080527120128.7074c1bc@werewolf.home>

J.A. Magallón wrote:
> On Mon, 26 May 2008 11:41:35 -0700 (PDT), Linus Torvalds <torvalds@linux-foundation.org> wrote:
> 
>> You know the drill by now: another week, another -rc.
>>
>> There's a lot of small stuff in here, most people won't even notice. The 
>> most noticeable thing is for all you 32-bit x86 people who use PAE 
>> (enabled by the HIGHMEM64G config option) due to having too much memory in 
>> your machine - mprotect() was broken due to some of the PAT fix/cleanup 
>> patches, causing the NX bit to be not set correctly.
>>
>> So if you had PAE enabled _and_ a recent enough CPU to have NX, but not 
>> recent enough to be 64-bit (or you were just perverse and wanted to run a 
>> 32-bit kernel despite having a chip that could do 64-bit and enough memory 
>> that you _really_ should have used a 64-bit kernel), you'd get various 
>> random program failures with SIGSEGV. It ranged from X not starting up to 
>> apparently OpenOffice not working if it did.
>>
>> But most of the changes, as usual, are in drivers, at 60%, with some DRI 
>> changes leading the way (fixing a number of other regressions, mainly by 
>> reverting the under-cooked vblank update). Network, MMC, USB, watchdog and 
>> IDE drivers also got updates.
>>
>> We had CIFS and NFS updates, and some arch updates as usual. The dirstat 
>> gives the overview:
>>
> 
> I have this patchsets collected from LKML, that still apply ontop of -rc4.
> Are they not so urgent or are they not needed any more ?
> 
> JBD[2] races
> http://marc.info/?l=linux-ext4&m=121141319601650&w=2
> http://marc.info/?l=linux-ext4&m=121141319701660&w=2
> 
Unless I misread the thread, akpm had a raft of issues with the first 
one, all of which were spelling except one initialization which he 
thought was not needed. All of those could be fixed in less effort that 
it takes to mention them, perhaps, but even so I think the patch could 
be ready in a short time.

The problem looks worth fixing to me, but probably not a must have at 
the rc4 level. Maybe in 2.6.27 we could get rid of the potential race?


-- 
Bill Davidsen <davidsen@tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot


      reply	other threads:[~2008-05-28 23:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.LFD.1.10.0805261127030.2958@woody.linux-foundation.org>
2008-05-27 10:01 ` Linux 2.6.26-rc4 J.A. Magallón
2008-05-28 23:59   ` Bill Davidsen [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=483DF1D5.9030706@tmr.com \
    --to=davidsen@tmr.com \
    --cc=jamagallon@ono.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).