From: Dongliang Mu <mudongliangabcd@gmail.com>
To: Sven Eckelmann <sven@narfation.org>
Cc: Marek Lindner <mareklindner@neomailbox.ch>,
Simon Wunderlich <sw@simonwunderlich.de>,
Antonio Quartulli <a@unstable.cc>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Antonio Quartulli <antonio@open-mesh.com>,
b.a.t.m.a.n@lists.open-mesh.org,
"open list:NETWORKING [GENERAL]" <netdev@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] net: batman-adv: fix warning in batadv_v_ogm_free
Date: Mon, 1 Nov 2021 16:11:18 +0800 [thread overview]
Message-ID: <CAD-N9QUFFchS=rWjy1GN14CKM+9NXE0C4tnR7zS3h-jZR_T9wA@mail.gmail.com> (raw)
In-Reply-To: <3170956.dbteMgFBTL@ripper>
On Mon, Nov 1, 2021 at 3:46 PM Sven Eckelmann <sven@narfation.org> wrote:
>
> On Monday, 1 November 2021 05:01:02 CET Dongliang Mu wrote:
> > Call Trace:
> > __cancel_work_timer+0x1c9/0x280 kernel/workqueue.c:3170
> > batadv_v_ogm_free+0x1d/0x50 net/batman-adv/bat_v_ogm.c:1076
> > batadv_mesh_free+0x35/0xa0 net/batman-adv/main.c:244
> > batadv_mesh_init+0x22a/0x240 net/batman-adv/main.c:226
> > batadv_softif_init_late+0x1ad/0x240 net/batman-adv/soft-interface.c:804
> > register_netdevice+0x15d/0x810 net/core/dev.c:10229
>
> This is definitely not a backtrace of the current code and its error handling.
> Please check the current code [1] and explain the situation against this
> version.
Yes, you're right. The error handling code in the upstream is not
prone to this bug.
My local syzkaller instance is fuzzing on 5.14-rc5
>
> Kind regards,
> Sven
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/tree/net/batman-adv/main.c?id=ae0393500e3b0139210749d52d22b29002c20e16#n237
prev parent reply other threads:[~2021-11-01 8:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 4:01 [PATCH] net: batman-adv: fix warning in batadv_v_ogm_free Dongliang Mu
2021-11-01 7:46 ` Sven Eckelmann
2021-11-01 8:11 ` Dongliang Mu [this message]
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='CAD-N9QUFFchS=rWjy1GN14CKM+9NXE0C4tnR7zS3h-jZR_T9wA@mail.gmail.com' \
--to=mudongliangabcd@gmail.com \
--cc=a@unstable.cc \
--cc=antonio@open-mesh.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mareklindner@neomailbox.ch \
--cc=netdev@vger.kernel.org \
--cc=sven@narfation.org \
--cc=sw@simonwunderlich.de \
/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).