All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+6f66f3e78821b0fff882@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, axboe@kernel.dk, dhowells@redhat.com,
	herbert@gondor.apana.org.au, kuba@kernel.org,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, netdev@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [block?] KASAN: slab-out-of-bounds Read in bio_split_rw
Date: Mon, 24 Jul 2023 10:20:45 -0700	[thread overview]
Message-ID: <000000000000bd577706013ed580@google.com> (raw)
In-Reply-To: <13125.1690215929@warthog.procyon.org.uk>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-and-tested-by: syzbot+6f66f3e78821b0fff882@syzkaller.appspotmail.com

Tested on:

commit:         0b7ec177 crypto: algif_hash - Fix race between MORE an..
git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=157554a1a80000
kernel config:  https://syzkaller.appspot.com/x/.config?x=bccf8d7311b80058
dashboard link: https://syzkaller.appspot.com/bug?extid=6f66f3e78821b0fff882
compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40

Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.

  reply	other threads:[~2023-07-24 17:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-04  1:45 [syzbot] [block?] KASAN: slab-out-of-bounds Read in bio_split_rw syzbot
2023-07-08 17:53 ` syzbot
2023-07-24 16:25   ` David Howells
2023-07-24 17:20     ` syzbot [this message]
2023-07-24 21:12   ` David Howells
2023-07-24 21:12     ` syzbot
2023-07-24 21:20   ` David Howells

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=000000000000bd577706013ed580@google.com \
    --to=syzbot+6f66f3e78821b0fff882@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=dhowells@redhat.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=kuba@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=netdev@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.