linux-kernel - Re: [git pull] IDE fixes

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <200906072308.13913.bzolnier@gmail.com>
Date:	Sun, 7 Jun 2009 23:08:13 +0200
From:	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>
To:	James Bottomley <James.Bottomley@...senpartnership.com>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-ide@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [git pull] IDE fixes

On Sunday 07 June 2009 22:39:45 James Bottomley wrote:
> On Sun, 2009-06-07 at 21:07 +0100, Alan Cox wrote:
> > > > [ I also tried to encourage libata developers to look into making the needed
> > > >   libata changes (see my initial posting of HPA patches) and I will still be
> > > >   glad to help with libata patches if somebody would like to work on them
> > > >   (Robert? Tejun?). ]
> > > 
> > > OK, so back off on the 2.6.30-rc7 release of this and I'll undertake to
> > > get libata engaged for integrating this into both subsystems for
> > > 2.6.31 ... does that sound fair?
> > 
> > libata already is, and I've been following and reviewing the patches. The
> > problem remaining is basically that this is not the time to merge
> > it.
> 
> Actually, I was talking about the fallback to disabling heuristic which
> this patch set introduces, and which would fix bug 13365 if it were
> applied to libata, but which is the bit I think needs some testing.

My patches fix the root cause of the problem and alleviate the issue for
all new installations.  In libata's case more testing is needed because
the libata's default is to keep HPA enabled (which is proper for modern
systems).

Once you get all HPA details (it is a complicated mess -- that is why
kernel/distributions couldn't get it right for years) you will see the
overall picture of the problem -- the work on multiple fronts at once
(including user-space) is needed to fix it properly.
--
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/