From: Dan Carpenter <dan.carpenter@oracle.com>
To: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
Cc: axboe@kernel.dk, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org,
syzbot+f08c77040fa163a75a46@syzkaller.appspotmail.com
Subject: Re: [PATCH] scsi: sd: Jump to out_free_index if device_add{,_disk}() fail
Date: Tue, 29 Mar 2022 10:47:45 +0300 [thread overview]
Message-ID: <20220329074744.GR12805@kadam> (raw)
In-Reply-To: <2179817.iZASKD2KPV@leap>
No, this patch is wrong. That is supposed to be freed in scsi_disk_release()
but apparently that's not getting called. Is the ref counting off?
On Tue, Mar 29, 2022 at 08:18:16AM +0200, Fabio M. De Francesco wrote:
> > There is a larger process issue here. We need to figure out why syzbot
> > did not detect that this patch introduces bugs.
>
> This is something that the people who run Syzbot/Syzkaller should help to
> figure out.
Yeah. Right now syzbot just says "TEST PASSED" but it doesn't give a
complete dmesg. There were other leaks on this path. Were they not
detected? We can't know without looking at the dmesg.
regards,
dan carpenter
next prev parent reply other threads:[~2022-03-29 7:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 8:44 [PATCH] scsi: sd: Jump to out_free_index if device_add{,_disk}() fail Fabio M. De Francesco
2022-03-28 14:38 ` Dan Carpenter
2022-03-29 6:18 ` Fabio M. De Francesco
2022-03-29 7:04 ` Christoph Hellwig
2022-03-29 7:47 ` Dan Carpenter [this message]
2022-03-29 7:57 ` Dan Carpenter
2022-03-29 8:28 ` Fabio M. De Francesco
2022-03-29 9:08 ` Dan Carpenter
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=20220329074744.GR12805@kadam \
--to=dan.carpenter@oracle.com \
--cc=axboe@kernel.dk \
--cc=fmdefrancesco@gmail.com \
--cc=jejb@linux.ibm.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=syzbot+f08c77040fa163a75a46@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 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.