[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM_iQpW7YtS2=rRw814=zWcJaUOGmkWQ+NHQKPwsBF4hMQSRVg@mail.gmail.com>
Date: Sat, 30 Sep 2017 17:22:33 -0700
From: Cong Wang <xiyou.wangcong@...il.com>
To: Vinicius Costa Gomes <vinicius.gomes@...el.com>
Cc: Linux Kernel Network Developers <netdev@...r.kernel.org>,
intel-wired-lan <intel-wired-lan@...ts.osuosl.org>,
Jesus Sanchez-Palencia <jesus.sanchez-palencia@...el.com>,
Jamal Hadi Salim <jhs@...atatu.com>,
Jiri Pirko <jiri@...nulli.us>, andre.guedes@...el.com,
Ivan Briano <ivan.briano@...el.com>, boon.leong.ong@...el.com,
richardcochran@...il.com, Henrik Austad <henrik@...tad.us>,
levipearson@...il.com, rodney.cummings@...com
Subject: Re: [next-queue PATCH v2 2/5] net/sched: Fix accessing invalid dev_queue
On Fri, Sep 29, 2017 at 5:26 PM, Vinicius Costa Gomes
<vinicius.gomes@...el.com> wrote:
> From: Jesus Sanchez-Palencia <jesus.sanchez-palencia@...el.com>
>
> In qdisc_alloc() the dev_queue pointer was used without any checks being
> performed. If qdisc_create() gets a null dev_queue pointer, it just
> passes it along to qdisc_alloc(), leading to a crash. That happens if a
> root qdisc implements select_queue() and returns a null dev_queue
> pointer for an "invalid handle", for example.
Does it make sense to let mqprio_select_queue() always return
non-NULL?
At least mq_select_queue() returns queue #0 as a fallback.
Powered by blists - more mailing lists