[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANn89iKxw4=29p_Ys3H0=mDQFOfZYbqxaTuLsRYK2X2tJCuwHQ@mail.gmail.com>
Date: Wed, 12 Feb 2025 10:47:08 +0100
From: Eric Dumazet <edumazet@...gle.com>
To: YAN KANG <kangyan91@...look.com>
Cc: Joel Granados <joel.granados@...nel.org>, "David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>, David Ahern <dsahern@...nel.org>,
"j.granados@...sung.com" <j.granados@...sung.com>, "linux@...ssschuh.net" <linux@...ssschuh.net>,
"judyhsiao@...omium.org" <judyhsiao@...omium.org>, "James.Z.Li@...l.com" <James.Z.Li@...l.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"syzkaller@...glegroups.com" <syzkaller@...glegroups.com>
Subject: Re: BUG: corrupted list in neigh_destroy [with reproducer]
On Wed, Feb 12, 2025 at 10:18 AM YAN KANG <kangyan91@...look.com> wrote:
>
> Hi:
>
> I found a kernel bug titiled "BUG: corrupted list in neigh_destroy " while using modified syzkaller fuzzing tool. I Itested it on the latest Linux upstream version (6.13.0-rc7), and it was able to be triggered. I found early report has no repro. I have a reproducer that can stable trigger this bug .
>
> early report: https://lore.kernel.org/netdev/20241007202240.bsqczev75yzdgn3g@joelS2.panther.com/
>
> The bug info is:
>
> kernel revision: v6.13-rc7
> OOPS message: BUG: corrupted list in neigh_destroy
> reproducer:YES
> subsystem: NETWORKING
FYI, there are already many public reports using bcachefs to trigger
'bugs' in networking or other layers.
Do not send other reports, or make sure your repro is _only_ using
networking stuff.
Powered by blists - more mailing lists