From: Jakub Kicinski <kuba@kernel.org>
To: Caleb Sander <csander@purestorage.com>
Cc: syzbot <syzbot+21ba4d5adff0b6a7cfc6@syzkaller.appspotmail.com>,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, parav@nvidia.com, saeedm@nvidia.com,
syzkaller-bugs@googlegroups.com, tariqt@nvidia.com
Subject: Re: [syzbot] [net?] general protection fault in dev_prep_valid_name
Date: Mon, 18 Nov 2024 18:53:23 -0800 [thread overview]
Message-ID: <20241118185323.37969bcd@kernel.org> (raw)
In-Reply-To: <CADUfDZqBUvm5vUgRHXKjvo=Kk4Ze8xU5tn-wG6J0wmUE6TTREA@mail.gmail.com>
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.
next prev parent reply other threads:[~2024-11-19 2:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-16 6:37 [syzbot] [net?] general protection fault in dev_prep_valid_name syzbot
2024-11-19 2:19 ` Caleb Sander
2024-11-19 2:53 ` Jakub Kicinski [this message]
2024-11-25 10:53 ` Aleksandr Nogikh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241118185323.37969bcd@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=csander@purestorage.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=parav@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=syzbot+21ba4d5adff0b6a7cfc6@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tariqt@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).