netdev - Re: net/ipv4/fib_trie.c:1550 suspicious rcu_dereference

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]

Date:	Tue, 10 Mar 2015 09:41:35 -0700
From:	Alexander Duyck <alexander.h.duyck@...hat.com>
To:	Fabio Estevam <festevam@...il.com>,
	"David S. Miller" <davem@...emloft.net>
CC:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	Olof Johansson <olof@...om.net>
Subject: Re: net/ipv4/fib_trie.c:1550 suspicious rcu_dereference_check() usage


On 03/10/2015 09:20 AM, Fabio Estevam wrote:
> On Tue, Mar 10, 2015 at 1:19 AM, Fabio Estevam <festevam@...il.com> wrote:
>> Hi,
>>
>> On a imx6sl-warp board running linux-next 20150306:
>>
>> root@...6sl-warp:~# reboot
>>
>> The system is going down for reboot NOW!(ttymxc0) (Wed Feb 25 18:41:59 2015):
>> INIT: Switching to runlevel: 6
>> INIT: Sending processes the TERM signal
>> INIT: Sending processe Stopping syslogd/klogd: stopped syslogd (pid 301)
>> stopped klogd (pid 304)
>> done
>> Deconfiguring network interfaces... [   36.083246]
>> [   36.084753] ===============================
>> [   36.089026] [ INFO: suspicious RCU usage. ]
>> [   36.093217] 4.0.0-rc2-next-20150306-00003-g62c7037-dirty #2699 Not tainted
> It seems that the issue is gone in linux-next 20150310.

I'll look into it just to make sure.  It likely means that there was a 
bug in the first set of patches that were accepted in the first half of 
last week that was likely resolved when the second set was accepted.

- Alex
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html