linux-kernel - Re: 2.6.34-rc2 breaks via82cxxx Host Protected Area

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]

Date:	Sun, 28 Mar 2010 13:48:00 +0200
From:	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	David Miller <davem@...emloft.net>, david@...es.net,
	jeff@...zik.org, linux-kernel@...r.kernel.org,
	linux-ide@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: 2.6.34-rc2 breaks via82cxxx Host Protected Area


Hi Stephen,

On Sunday 28 March 2010 05:01:41 am Stephen Rothwell wrote:
> Hi Bart,
> 
> On Sat, 27 Mar 2010 16:34:08 +0100 Bartlomiej Zolnierkiewicz <bzolnier@...il.com> wrote:
> >
> > On Saturday 27 March 2010 03:44:34 pm David Miller wrote:
> > > From: Bartlomiej Zolnierkiewicz <bzolnier@...il.com>
> > > Date: Sat, 27 Mar 2010 11:19:53 +0100
> > > 
> > > > The commit itself may also have a problem but since it was _never_ in
> > > > linux-next tree it never saw a wider upstream testing.
> > > 
> > > This is not true Bart.
> > 
> > Uh?  I had verified my claims before writing previous mail..
> > 
> > The patch ("via82cxxx: workaround h/w bugs") appeared in Linus'
> > tree on 19th January and it was neither in next-20100101 nor in
> > next-20100119.. etc.
> 
> That commit first appeared in linux-next in next-20100120 as part of
> Dave's ide tree.  It was merged into Linus' tree on March 5th (commit
> 4c10c937cc2eb197db565392db91d429eec71176 "Merge
> git://git.kernel.org/pub/scm/linux/kernel/git/davem/ide-next-2.6").

Which doesn't change a bit the fundamental fact that the patch was not
meant for upstream by me and was clearly marked as such.  If David wanted
it upstream he should either be ready to provide support for it himself
or solve it in a more formal way..

--
Bartlomiej Zolnierkiewicz
--
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/