[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3100603.HWLWhOUWpG@sven-edge>
Date: Sun, 30 Dec 2018 12:00:12 +0100
From: Sven Eckelmann <sven@...fation.org>
To: syzbot <syzbot+c764de0fcfadca9a8595@...kaller.appspotmail.com>
Cc: a@...table.cc, b.a.t.m.a.n@...ts.open-mesh.org,
davem@...emloft.net, linux-kernel@...r.kernel.org,
mareklindner@...mailbox.ch, netdev@...r.kernel.org,
sw@...onwunderlich.de, syzkaller-bugs@...glegroups.com
Subject: Re: WARNING in batadv_is_on_batman_iface
On Sunday, 30 December 2018 11.41.03 CET syzbot wrote:
[...]
> HEAD commit: d8924c0d76aa Merge tag 'devprop-4.21-rc1' of git://git.ker..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=122a373f400000
> kernel config: https://syzkaller.appspot.com/x/.config?x=91a256823ef17263
> dashboard link: https://syzkaller.appspot.com/bug?extid=c764de0fcfadca9a8595
> compiler: gcc (GCC) 8.0.1 20180413 (experimental)
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16fd1d67400000
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+c764de0fcfadca9a8595@...kaller.appspotmail.com
What is the bug here? The kernel module showed a warning because the parent
device cannot be found in the same netns using __dev_get_by_index.
The test system was just configured to panic on warnings. So are we now
expected to show warnings or what is the expected behavior?
This behavior was added with commit b7eddd0b3950 ("batman-adv: prevent using
any virtual device created on batman-adv as hard-interface") - 3d48811b27f5 in
the out-of-tree module.
Kind regards,
Sven
[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b7eddd0b3950ea9dc863f1cbfa30d172dbf772f4
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists