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: <20120807114556.GC16861@opensource.wolfsonmicro.com>
Date:	Tue, 7 Aug 2012 12:45:57 +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:36:52PM +0100, Russell King wrote:

> And, for those hard of thinking, I'll tell you exactly how invasive it
> is.

> 1. You modify ioport.h to add the new type.

> Yes, it's really that damned simple.  Not invasive at all.

Your step 1 is the bit that strikes me as invasive here - that's not
something I'd be touching in a stable release if I didn't have to, it's
visible to half the kernel in an area where we clearly don't have ideal
review of the code (otherwise we'd not have a problem here in the first
place) which seems totally disproportionate to the benefit here.  We're
talking about an issue which affects one device which is used only on
Marvell systems here.

I think everyone agrees that this is the best route forward for future
kernels.
--
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/