[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANn89iJu3NzBS+bQHJ_X427SAVgr2HB=fBr8MADhD_hAqKmhHw@mail.gmail.com>
Date: Fri, 18 Nov 2022 07:04:44 -0800
From: Eric Dumazet <edumazet@...gle.com>
To: Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>
Cc: "David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>,
David Ahern <dsahern@...nel.org>,
Jakub Sitnicki <jakub@...udflare.com>,
Tom Parkin <tparkin@...alix.com>,
syzbot <syzbot+703d9e154b3b58277261@...kaller.appspotmail.com>,
netdev@...r.kernel.org, syzkaller-bugs@...glegroups.com,
Haowei Yan <g1042620637@...il.com>
Subject: Re: [PATCH 6.1-rc6] l2tp: call udp_tunnel_encap_enable() and
sock_release() without sk_callback_lock
On Fri, Nov 18, 2022 at 5:19 AM Tetsuo Handa
<penguin-kernel@...ove.sakura.ne.jp> wrote:
>
> On 2022/11/18 21:36, Eric Dumazet wrote:
> > Please look at recent discussion, your patch does not address another
> > fundamental problem.
> >
> > Also, Jakub was working on a fix already. Perhaps sync with him to
> > avoid duplicate work.
>
> I can't afford monitoring all mailing lists. Since a thread at syzkaller-bugs group
> did not get that information, I started this work. Please consider including
> syzbot+XXXXXXXXXXXXXXXXXXXX@...kaller.appspotmail.com into the discussions so that
> we can google for recent discussions (if any) using mail address as a keyword.
>
This is not going to happen.
The discussion happened before the reports were made public.
No more than 7 syzbot reports are attached to the same root cause.
We deal with hundreds of syzbot reports per week, there is no way we
can retroactively find all relevant netdev@ threads.
If you can not afford making sure you are not wasting your time, this
is your call.
Powered by blists - more mailing lists