linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+313d95e8a7a49263f88d@syzkaller.appspotmail.com>
To: a@unstable.cc, axboe@kernel.dk, b.a.t.m.a.n@lists.open-mesh.org,
	bvanassche@acm.org, davem@davemloft.net, dongli.zhang@oracle.com,
	hdanton@sina.com, jianchao.w.wang@oracle.com,
	linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, mareklindner@neomailbox.ch,
	netdev@vger.kernel.org, sven@narfation.org,
	sw@simonwunderlich.de, syzkaller-bugs@googlegroups.com,
	viro@zeniv.linux.org.uk
Subject: Re: KASAN: null-ptr-deref Write in blk_mq_map_swqueue
Date: Wed, 24 Jun 2020 20:01:11 -0700	[thread overview]
Message-ID: <00000000000006e0ff05a8dfce2d@google.com> (raw)
In-Reply-To: <00000000000047770d05a1c70ecb@google.com>

This bug is marked as fixed by commit:
blk-mq: Fix a recently introduced regression in
But I can't find it in any tested tree for more than 90 days.
Is it a correct commit? Please update it by replying:
#syz fix: exact-commit-title
Until then the bug is still considered open and
new crashes with the same signature are ignored.

  parent reply	other threads:[~2020-06-25  3:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <00000000000047770d05a1c70ecb@google.com>
2020-03-27  1:28 ` KASAN: null-ptr-deref Write in blk_mq_map_swqueue syzbot
2020-03-27  3:00   ` Bart Van Assche
2020-03-27 15:06   ` Jens Axboe
2020-06-25  3:01 ` syzbot [this message]
2020-06-25  4:05   ` Bart Van Assche

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=00000000000006e0ff05a8dfce2d@google.com \
    --to=syzbot+313d95e8a7a49263f88d@syzkaller.appspotmail.com \
    --cc=a@unstable.cc \
    --cc=axboe@kernel.dk \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=bvanassche@acm.org \
    --cc=davem@davemloft.net \
    --cc=dongli.zhang@oracle.com \
    --cc=hdanton@sina.com \
    --cc=jianchao.w.wang@oracle.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mareklindner@neomailbox.ch \
    --cc=netdev@vger.kernel.org \
    --cc=sven@narfation.org \
    --cc=sw@simonwunderlich.de \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=viro@zeniv.linux.org.uk \
    /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).