linux-kernel - 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20241118185323.37969bcd@kernel.org>
Date: Mon, 18 Nov 2024 18:53:23 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Caleb Sander <csander@...estorage.com>
Cc: 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 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.