On Tue 17 Sep 2019 at 20:03, Cong Wang wrote:
> On Tue, Sep 17, 2019 at 1:27 AM Vlad Buslov wrote:
>> Hi Cong,
>>
>> Don't see why we would need qdisc tree lock while releasing the
>> reference to (or destroying) previous Qdisc. I've skimmed through other
>> scheds and it looks like sch_multiq,
On Tue, Sep 17, 2019 at 1:27 AM Vlad Buslov wrote:
> Hi Cong,
>
> Don't see why we would need qdisc tree lock while releasing the
> reference to (or destroying) previous Qdisc. I've skimmed through other
> scheds and it looks like sch_multiq, sch_htb and sch_tbf are also
> affected. Do you want me
On Tue 17 Sep 2019 at 04:58, Cong Wang wrote:
> On Mon, Sep 16, 2019 at 4:39 PM syzbot
> wrote:
>>
>> Hello,
>>
>> syzbot found the following crash on:
>>
>> HEAD commit:1609d760 Merge tag 'for-linus' of git://git.kernel.org/pub..
>> git tree: upstream
>> console output: https://syzka
On Mon, Sep 16, 2019 at 4:39 PM syzbot
wrote:
>
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:1609d760 Merge tag 'for-linus' of git://git.kernel.org/pub..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=10236abe60
> kernel config:
Hello,
syzbot found the following crash on:
HEAD commit:1609d760 Merge tag 'for-linus' of git://git.kernel.org/pub..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10236abe60
kernel config: https://syzkaller.appspot.com/x/.config?x=ed2b148cd67382ec
da
5 matches
Mail list logo