[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAM_iQpWWSO_RBE-1ja0N88=ZedmCU4J37CyoQ=zME=Q0Fiq_Xg@mail.gmail.com>
Date: Thu, 12 Sep 2019 09:48:38 -0700
From: Cong Wang <xiyou.wangcong@...il.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Eric Dumazet <eric.dumazet@...il.com>,
Linux Kernel Network Developers <netdev@...r.kernel.org>,
syzbot <syzbot+d5870a903591faaca4ae@...kaller.appspotmail.com>,
Jamal Hadi Salim <jhs@...atatu.com>,
Jiri Pirko <jiri@...nulli.us>
Subject: Re: [Patch net] sch_sfb: fix a crash in sfb_destroy()
On Thu, Sep 12, 2019 at 3:31 AM Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> On Thu, Sep 12, 2019 at 2:10 AM Cong Wang <xiyou.wangcong@...il.com> wrote:
> >
> > On Wed, Sep 11, 2019 at 2:36 PM Eric Dumazet <eric.dumazet@...il.com> wrote:
> > >
> > > It seems a similar fix would be needed in net/sched/sch_dsmark.c ?
> > >
> >
> > Yeah, or just add a NULL check in dsmark_destroy().
>
> Well, this was why one of my suggestions was to just make
> "qdisc_put()" be happy with a NULL pointer (or even an ERR_PTR()).
>
> That would have fixed not just sfb, but also dsmark with a single patch.
Sure, I don't have any preference here, just want to find a minimum
fix for -stable.
I will send v2.
Thanks.
Powered by blists - more mailing lists