On Fri, Jan 22, 2021 at 6:47 AM 慕冬亮 wrote:
>
> On Thu, Jan 21, 2021 at 8:49 PM Lukas Bulwahn wrote:
> >
> > On Thu, Jan 21, 2021 at 6:37 AM 慕冬亮 wrote:
> > >
> > > Dear kernel developers,
> > >
> > > I found that on the syzbot dashboard, “possible deadlock in
> > >
On Thu, Jan 21, 2021 at 8:49 PM Lukas Bulwahn wrote:
>
> On Thu, Jan 21, 2021 at 6:37 AM 慕冬亮 wrote:
> >
> > Dear kernel developers,
> >
> > I found that on the syzbot dashboard, “possible deadlock in
> > console_lock_spinning_enable”[1] and "possible deadlock in
> > console_unlock"[2] should
On Thu, Jan 21, 2021 at 6:37 AM 慕冬亮 wrote:
>
> Dear kernel developers,
>
> I found that on the syzbot dashboard, “possible deadlock in
> console_lock_spinning_enable”[1] and "possible deadlock in
> console_unlock"[2] should share the same root cause.
>
> The reasons for the above statement:
> 1)
On Thu, Jan 21, 2021 at 01:37:05PM +0800, 慕冬亮 wrote:
> Dear kernel developers,
>
> I found that on the syzbot dashboard, “possible deadlock in
> console_lock_spinning_enable”[1] and "possible deadlock in
> console_unlock"[2] should share the same root cause.
>
> The reasons for the above
Dear kernel developers,
I found that on the syzbot dashboard, “possible deadlock in
console_lock_spinning_enable”[1] and "possible deadlock in
console_unlock"[2] should share the same root cause.
The reasons for the above statement:
1) the stack trace is the same, and this title difference is
5 matches
Mail list logo