linux-kernel - Re: [PATCH 1/6] ide: fix setting nIEN on idle devices

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: <20081216202436.GA2506@1wt.eu>
Date:	Tue, 16 Dec 2008 21:24:36 +0100
From:	Willy Tarreau <w@....eu>
To:	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>
Cc:	linux-ide@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/6] ide: fix setting nIEN on idle devices

On Tue, Dec 16, 2008 at 07:57:52PM +0100, Bartlomiej Zolnierkiewicz wrote:
> On Sunday 14 December 2008, Willy Tarreau wrote:
> > Hi Bart,
> > 
> > On Sun, Dec 14, 2008 at 12:39:32AM +0100, Bartlomiej Zolnierkiewicz wrote:
> > > From: Bartlomiej Zolnierkiewicz <bzolnier@...il.com>
> > > Subject: [PATCH] ide: fix setting nIEN on idle devices
> > > 
> > > Fix do_ide_request() to operate on previous device / port instead of
> > > the current one.  The original code was wrong since at least Feb 2002
> > > (2.4.0 timeframe).
> > 
> > What could be the impact of this bug ? Should I backport your fix to 2.4 ?
> 
> The fix results in better handling of unexpected IRQs on serialized IDE
> ports.  However since unexpected IRQs coming from a device is not something
> we should normally see and I don't recall seeing any bugreports that would
> be potentially closed by this fix I don't think that there is an urgent need
> to backport it (thanks for caring about 2.4.x users anyway!).

OK, thanks Bart !
Willy

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