From: Johannes Berg <johannes@sipsolutions.net>
To: syzbot <syzbot+5f9392825de654244975@syzkaller.appspotmail.com>,
a@unstable.cc, b.a.t.m.a.n@lists.open-mesh.org,
davem@davemloft.net, david@fromorbit.com, dchinner@redhat.com,
hch@lst.de, kuba@kernel.org, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org, mareklindner@neomailbox.ch,
netdev@vger.kernel.org, sw@simonwunderlich.de,
syzkaller-bugs@googlegroups.com
Subject: Re: WARNING in cfg80211_connect
Date: Fri, 02 Oct 2020 08:26:50 +0200 [thread overview]
Message-ID: <7bf217ced62816b1bd3404bcfe279082347fb265.camel@sipsolutions.net> (raw)
In-Reply-To: <0000000000000a954d05b0a89a86@google.com> (sfid-20201002_063111_703712_8FE82506)
On Thu, 2020-10-01 at 21:31 -0700, syzbot wrote:
> syzbot has bisected this issue to:
>
> commit 16d4d43595b4780daac8fcea6d042689124cb094
> Author: Christoph Hellwig <hch@lst.de>
> Date: Wed Jul 20 01:38:55 2016 +0000
>
> xfs: split direct I/O and DAX path
>
LOL!
Unlike in many other cases, here I don't even see why it went down that
path. You'd think that Christoph's commit should have no effect
whatsoever, but here we are with syzbot claiming a difference?
I mean, often enough it says something is "caused" by a patch because
that caused e.g. generic netlink family renumbering, or because it
emitted some other ioctl() calls or whatnot that are invalid before and
valid after some other (feature) patch (or vice versa sometimes), but
you'd think that this patch would have _zero_ userspace observable
effect?
Which I guess means that the reproduction of this bug is random, perhaps
timing related.
johannes
next prev parent reply other threads:[~2020-10-02 6:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 10:28 WARNING in cfg80211_connect syzbot
2020-10-01 21:32 ` syzbot
2020-10-02 4:31 ` syzbot
2020-10-02 6:26 ` Johannes Berg [this message]
2020-10-02 7:48 ` Dmitry Vyukov
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=7bf217ced62816b1bd3404bcfe279082347fb265.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=a@unstable.cc \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=davem@davemloft.net \
--cc=david@fromorbit.com \
--cc=dchinner@redhat.com \
--cc=hch@lst.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mareklindner@neomailbox.ch \
--cc=netdev@vger.kernel.org \
--cc=sw@simonwunderlich.de \
--cc=syzbot+5f9392825de654244975@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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).