linux-kernel - Re: [PATCH] kernel: replace strict

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]

Date:	Fri, 27 Sep 2013 19:09:51 -0500
From:	Bruno Wolff III <bruno@...ff.to>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Jean Delvare <khali@...ux-fr.org>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	Jingoo Han <jg1.han@...sung.com>, linux-kernel@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH] kernel: replace strict_strto*() with kstrto*()

On Fri, Sep 27, 2013 at 13:18:20 -0700,
   Andrew Morton <akpm@...ux-foundation.org> wrote:
>On Fri, 27 Sep 2013 19:53:53 +0200 Jean Delvare <khali@...ux-fr.org> wrote:
>
>> Andrew,
>>
>> On Fri, 27 Sep 2013 09:50:39 -0600, Bjorn Helgaas wrote:
>> > There's some indication that this change might have broken handling of
>> > signed types.  See
>> > https://lists.ozlabs.org/pipermail/linuxppc-dev/2013-September/111758.html
>> > and https://bugzilla.kernel.org/show_bug.cgi?id=61811.
>>
>> It seems this is hurting more users than I would have expected, and
>> people are spending significant amounts of time to figure out what the
>> root cause to their problem is. May I suggest that my fix should find
>> its way to Linus' tree rather sooner than later?
>>
>
>Done.  I had to send that one by hand as I'm not at my desk...

I just did a successful test of the patch from the mailing list. So it at 
least solved the problem in my case.
--
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/