From: Jet Chen <jet.chen@intel.com>
To: Cong Wang <cwang@twopensource.com>
Cc: Steffen Klassert <steffen.klassert@secunet.com>,
netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Fengguang Wu <fengguang.wu@intel.com>
Subject: Re: [net] WARNING: CPU: 1 PID: 1 at net/batman-adv/hard-interface.c:92 batadv_is_on_batman_iface()
Date: Thu, 22 May 2014 15:34:01 +0800 [thread overview]
Message-ID: <537DA869.9070108@intel.com> (raw)
In-Reply-To: <CAHA+R7Mhd2KYaU8THAd+O4HzQNRLxhpGccvEPOqWJRKAwZbpgQ@mail.gmail.com>
On 05/22/2014 02:12 PM, Cong Wang wrote:
> On Wed, May 21, 2014 at 9:42 PM, Jet Chen <jet.chen@intel.com> wrote:
>> Hi Steffen,
>>
>> 0day kernel testing robot got the below dmesg and the first bad commit is
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git master
>> commit 78ff4be45a4c51d8fb21ad92e4fabb467c6c3eeb
>> Author: Steffen Klassert <steffen.klassert@secunet.com>
>> AuthorDate: Mon May 19 11:36:56 2014 +0200
>> Commit: David S. Miller <davem@davemloft.net>
>> CommitDate: Wed May 21 02:08:32 2014 -0400
>>
>> ip_tunnel: Initialize the fallback device properly
>> We need to initialize the fallback device to have a correct mtu
>> set on this device. Otherwise the mtu is set to null and the device
>> is unusable.
>> Fixes: fd58156e456d ("IPIP: Use ip-tunneling code.")
>> Cc: Pravin B Shelar <pshelar@nicira.com>
>> Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>
>> Signed-off-by: David S. Miller <davem@davemloft.net>
>>
>> +--------------------------------------------------------------------------------+------------+------------+
>> |
>> | d8d33c3b8a | 78ff4be45a |
>> +--------------------------------------------------------------------------------+------------+------------+
>> | boot_successes
>> | 60 | 0 |
>> | boot_failures
>> | 0 | 20 |
>> |
>> WARNING:CPU:PID:at_net/batman-adv/hard-interface.c:batadv_is_on_batman_iface()
>> | 0 | 20 |
>> | backtrace:register_netdevice_notifier
>> | 0 | 20 |
>> | backtrace:batadv_init
>> | 0 | 20 |
>> | backtrace:kernel_init_freeable
>> | 0 | 20 |
>> +--------------------------------------------------------------------------------+------------+------------+
>>
>
> batman needs to fix:
>
> diff --git a/net/batman-adv/hard-interface.c b/net/batman-adv/hard-interface.c
> index b851cc5..fbda6b5 100644
> --- a/net/batman-adv/hard-interface.c
> +++ b/net/batman-adv/hard-interface.c
> @@ -83,7 +83,7 @@ static bool batadv_is_on_batman_iface(const struct
> net_device *net_dev)
> return true;
>
> /* no more parents..stop recursion */
> - if (net_dev->iflink == net_dev->ifindex)
> + if (net_dev->iflink == 0 || net_dev->iflink == net_dev->ifindex)
> return false;
>
> /* recurse over the parent device */
>
Your patch fixes that issue.
Tested-by: Jet Chen <jet.chen@intel.com>
Thanks,
Jet
next prev parent reply other threads:[~2014-05-22 7:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 4:42 [net] WARNING: CPU: 1 PID: 1 at net/batman-adv/hard-interface.c:92 batadv_is_on_batman_iface() Jet Chen
2014-05-22 6:12 ` Cong Wang
2014-05-22 7:34 ` Jet Chen [this message]
2014-05-22 8:29 ` Steffen Klassert
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=537DA869.9070108@intel.com \
--to=jet.chen@intel.com \
--cc=cwang@twopensource.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).