From: Alexander Duyck <alexander.h.duyck@redhat.com>
To: Fabio Estevam <festevam@gmail.com>,
"David S. Miller" <davem@davemloft.net>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Olof Johansson <olof@lixom.net>
Subject: Re: net/ipv4/fib_trie.c:1550 suspicious rcu_dereference_check() usage
Date: Tue, 10 Mar 2015 09:41:35 -0700 [thread overview]
Message-ID: <54FF1EBF.10801@redhat.com> (raw)
In-Reply-To: <CAOMZO5C4Tg12r7W7msm_KPEhV1QxR1Uij-f_UBtVRUeTFxzn_w@mail.gmail.com>
On 03/10/2015 09:20 AM, Fabio Estevam wrote:
> On Tue, Mar 10, 2015 at 1:19 AM, Fabio Estevam <festevam@gmail.com> wrote:
>> Hi,
>>
>> On a imx6sl-warp board running linux-next 20150306:
>>
>> root@imx6sl-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
next prev parent reply other threads:[~2015-03-10 16:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 4:19 net/ipv4/fib_trie.c:1550 suspicious rcu_dereference_check() usage Fabio Estevam
2015-03-10 16:20 ` Fabio Estevam
2015-03-10 16:41 ` Alexander Duyck [this message]
2015-03-10 16:52 ` Alexander Duyck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54FF1EBF.10801@redhat.com \
--to=alexander.h.duyck@redhat.com \
--cc=davem@davemloft.net \
--cc=festevam@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olof@lixom.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.