linux-kernel - Re: [PULL] param sysfs oops (simple, leaky) fix, bool arrays fix

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: <s5h39y5v985.wl%tiwai@suse.de>
Date:	Thu, 06 May 2010 08:24:10 +0200
From:	Takashi Iwai <tiwai@...e.de>
To:	dedekind1@...il.com
Cc:	Rusty Russell <rusty@...tcorp.com.au>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Sitsofe Wheeler <sitsofe@...oo.com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Christof Schmitt <christof.schmitt@...ibm.com>
Subject: Re: [PULL] param sysfs oops (simple, leaky) fix, bool arrays fix

At Wed, 05 May 2010 12:04:18 +0300,
Artem Bityutskiy wrote:
> 
> On Wed, 2010-05-05 at 11:49 +0300, Artem Bityutskiy wrote:
> > > Fixing in the way of the later upstream is a bit too intrusive as a
> > > stable patch.  So, I'm also not sure whether we should take it,
> > > too...
> > 
> > To be frank I do not really understand what you mean.
> 
> If you meant 'let's not change it 2.6.34' - fair enough, it was already
> in 2.6.32, so there is probably no reason to hurry. But I suggest to
> still consider this as a big issue and fix as soon as we can.

Ah, sorry I was confused.  I somehow thought Rusty's patch has been
already merged after 2.6.32, but it didn't happen in reality.

Then I'm for merging the changes even for 2.6.34 although it's late.
In the API side, there aren't many changes.  And it might reduce the
whole binary size in the end by the use of module_parm_ops pointer,
too.


thanks,

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