linux-kernel - Re: [PATCH 0/5] mfd: replace IORESOURCE_IO by IORESOURCE

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: <20120807112844.GZ16861@opensource.wolfsonmicro.com>
Date:	Tue, 7 Aug 2012 12:28:44 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Russell King <rmk@....linux.org.uk>
Cc:	Haojian Zhuang <haojian.zhuang@...il.com>, sameo@...ux.intel.com,
	rpurdie@...ys.net, bryan.wu@...onical.com,
	linux-kernel@...r.kernel.org, Bergmann Arnd <arnd@...db.de>
Subject: Re: [PATCH 0/5] mfd: replace IORESOURCE_IO by IORESOURCE_MEM

On Tue, Aug 07, 2012 at 12:13:31PM +0100, Russell King wrote:
> On Tue, Aug 07, 2012 at 11:38:51AM +0100, Mark Brown wrote:

> > If nothing else this seems much more suitable for stable and -rc (the
> > bug has been there since v3.4).

> There is no need for such hacks.

Please read the text you quoted above.

> There's no need to botch this in any way what so ever, or invent some
> other solution only to have to (probably never) rework it.

The changes you're suggesting are extremely invasive for stable
especially given that we have a simple, driver local, fix available
which is already deployed and used in other drivers in the same kernels
(at least in v3.5 anyway, the change introducing the issue got pushed
into v3.4 unexpectedly so the fix didn't make it).  It would be worrying
if such changes were being accepted into stable.

I agree that the changes you're suggeting seem sensible for v3.7 if
someone wants to work on them, possibly even v3.6 if people are willing
to do something like that after the merge window, but we've got an issue
in stable here which is the most urgent thing.
--
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/