linux-kernel - Re: [PATCH] mce: fix fail to set 'monarchtimeout' via boot option

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: <555D2E10.4040509@huawei.com>
Date:	Thu, 21 May 2015 09:00:00 +0800
From:	Xie XiuQi <xiexiuqi@...wei.com>
To:	Borislav Petkov <bp@...en8.de>
CC:	<tony.luck@...el.com>, <tglx@...utronix.de>, <mingo@...hat.com>,
	<hpa@...or.com>, <x86@...nel.org>, <linux-edac@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] mce: fix fail to set 'monarchtimeout' via boot option

On 2015/5/21 1:43, Borislav Petkov wrote:
> On Wed, May 20, 2015 at 07:22:23PM +0800, Xie XiuQi wrote:
>> I use "mce=1,10000000" in cmdline to change the monarch timeout, but
>> it does not work.
>>
>> The cause is that get_option() has parsed the ',' already, we need
>> not to check the ',' again.
>>
>> --
>> get_option(): read an int from an option string;
>> if available accept a subsequent comma as well.
>>
>> Return values:
>> 0 - no int in string
>> 1 - int found, no subsequent comma
>> 2 - int found including a subsequent comma
>> 3 - hyphen found to denote a range
>>
>> Cc: <stable@...r.kernel.org>	# 2.6.32+
> 
> I don't think that's a serious enough a bug to justify the stable tag.
> 
>> Signed-off-by: Xie XiuQi <xiexiuqi@...wei.com>
>> ---

...

>>  		return 0;
> 
> Anyway, I fixed it up and applied it.

Sorry, I will check carefully next time.

Thanks.

> 
> Thanks.
> 


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