[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM_iQpU-yNPQK1VBgfP9d=y80Gyh57VUrP6nxT5nKk=fF5_Stg@mail.gmail.com>
Date: Mon, 19 Apr 2021 12:19:24 -0700
From: Cong Wang <xiyou.wangcong@...il.com>
To: Du Cheng <ducheng2@...il.com>
Cc: Jamal Hadi Salim <jhs@...atatu.com>, Jiri Pirko <jiri@...nulli.us>,
Linux Kernel Network Developers <netdev@...r.kernel.org>,
Shuah Khan <skhan@...uxfoundation.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Eric Dumazet <eric.dumazet@...il.com>,
syzbot+d50710fd0873a9c6b40c@...kaller.appspotmail.com
Subject: Re: [PATCH v4] net: sched: tapr: prevent cycle_time == 0 in parse_taprio_schedule
On Fri, Apr 16, 2021 at 4:30 PM Du Cheng <ducheng2@...il.com> wrote:
>
> There is a reproducible sequence from the userland that will trigger a WARN_ON()
> condition in taprio_get_start_time, which causes kernel to panic if configured
> as "panic_on_warn". Catch this condition in parse_taprio_schedule to
> prevent this condition.
>
> Reported as bug on syzkaller:
> https://syzkaller.appspot.com/bug?extid=d50710fd0873a9c6b40c
>
> Reported-by: syzbot+d50710fd0873a9c6b40c@...kaller.appspotmail.com
> Signed-off-by: Du Cheng <ducheng2@...il.com>
Acked-by: Cong Wang <cong.wang@...edance.com>
Thanks.
Powered by blists - more mailing lists