linux-kernel - Re: [PATCH 2/2] fs/partition/msdos: Fix unusable extended partition for

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20100312154415.a2f8f944.akpm@linux-foundation.org>
Date:	Fri, 12 Mar 2010 15:44:15 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Daniel Taylor <Daniel.Taylor@....com>,
	OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>,
	linux-kernel@...r.kernel.org, stable@...nel.org
Subject: Re: [PATCH 2/2] fs/partition/msdos: Fix unusable extended partition
 for > 512B sector

On Thu, 11 Mar 2010 14:09:09 -0800
"H. Peter Anvin" <hpa@...or.com> wrote:

> On 03/11/2010 02:06 PM, Daniel Taylor wrote:
> >
> > BIOS failures prior to loading the kernel are not Linux'
> > responsibility.  Confused BIOS will still fail, even if the
> > patch is not implemented,  so how does that effect the
> > acceptance of a patch that fixes post-boot behavior?
> >
> 
> I didn't say it does.
> 
> >>
> >> I would consider this a bugfix.  As such, it should be pushed outside
> >> the merge window.
> >>
> 
> Just in case I wasn't clear enough -- this patch is a bugfix and should 
> be pushed upstream as long as it is technically ready.
> 

yeah.  In fact I tagged it for -stable backporting.  Because as Daniel
says, "In the near future, WD will be releasing products that need this
patch".  People will surely want to use 2.6.33.x-based kernels with
those devices, so packagers of 2.6.33.x-based kernels will need to hunt
down and apply this patch.  So let's do it for them.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/