netdev - Re: [syzbot] [net?] general protection fault in dev_prep_valid

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CANp29Y7XjPwy3VxR-naQ-qjMZF63j9kh7fFmVH91HaSJ8i9ZMA@mail.gmail.com>
Date: Mon, 25 Nov 2024 11:53:51 +0100
From: Aleksandr Nogikh <nogikh@...gle.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Caleb Sander <csander@...estorage.com>, 
	syzbot <syzbot+21ba4d5adff0b6a7cfc6@...kaller.appspotmail.com>, 
	andrew+netdev@...n.ch, davem@...emloft.net, edumazet@...gle.com, 
	linux-kernel@...r.kernel.org, netdev@...r.kernel.org, pabeni@...hat.com, 
	parav@...dia.com, saeedm@...dia.com, syzkaller-bugs@...glegroups.com, 
	tariqt@...dia.com
Subject: Re: [syzbot] [net?] general protection fault in dev_prep_valid_name

On Tue, Nov 19, 2024 at 3:53 AM 'Jakub Kicinski' via syzkaller-bugs
<syzkaller-bugs@...glegroups.com> wrote:
>
> On Mon, 18 Nov 2024 18:19:23 -0800 Caleb Sander wrote:
> > Hmm, it seems very unlikely that "mlx5/core: Schedule EQ comp tasklet
> > only if necessary" could have caused this issue. The commit only
> > touches the mlx5 driver. Does the test machine have ConnectX NICs? The
> > commit itself simply moves where tasklet_schedule() is called for the
> > mlx5_cq_tasklet_cb() tasklet, making it so the tasklet will only be
> > scheduled to process userspace RDMA completions.
> > Is it possible that the failure is not consistently reproducible and
> > the bisection is landing on the wrong commit?
>
> Yes, most likely bad bisection, I looked at the syzbot docs but I don't
> see the command for invalidating the bisection results.
>

Thanks for analyzing the bisection!

It's indeed not possible to cancel the result via an email command.
I've marked it as invalid using other means and left a comment on the
corresponding backlog issue:
https://github.com/google/syzkaller/issues/5414#issuecomment-2497667350

-- 
Aleksandr