From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Wenchao Hao <haowenchao@huawei.com>,
syzkaller-bugs@googlegroups.com, axboe@kernel.dk,
jejb@linux.ibm.com, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
martin.petersen@oracle.com,
syzbot+f08c77040fa163a75a46@syzkaller.appspotmail.com,
linfeilong@huawei.com
Subject: Re: [PATCH] scsi: sd: call device_del() if device_add_disk() fails
Date: Thu, 31 Mar 2022 19:21:13 +0200 [thread overview]
Message-ID: <3427592.iIbC2pHGDl@leap> (raw)
In-Reply-To: <20220331162416.GI12805@kadam>
On gioved? 31 marzo 2022 18:24:16 CEST Dan Carpenter wrote:
> On Thu, Mar 31, 2022 at 06:14:27PM +0200, Fabio M. De Francesco wrote:
> > On gioved? 31 marzo 2022 15:42:10 CEST Dan Carpenter wrote:
> > > Wenchao Hao, what you're saying makes a lot of sense but it raises a lot
> > > of questions in turn.
> > >
> > > Fabio, did you test your patch?
> >
> > Yes, I did, Dan. I tested it the usual way with the "#syz test:" command.
> > Obviously I have not the hardware to test code on it.
> >
>
> Yeah. What a nightmare. You posted a link to the first test. It said
> passed but definitely introduced some use after frees but how was anyone
> supposed to know?
Maybe that a "spare-time Linux developer" like me should leave these
kinds of bug fixes to more experienced people. But we should also note
that I tried two or three different patches and _all_ of them passed
the tests.
>
> No way we would have figured this out.
I think that something should change about the way Syzbot tests patches
and about how it provides the results. The other four or five bugs that
I have fixed were based mainly to the fact that they passed the Syzbot
tests.
Perhaps I've been lucky but my patches were good and they were merged.
However, I began to trust Syzbot too much. This is not how I should
approach and try to solve bugs.
> I'm working to make Smatch
> understand device_put() better but this one is way difficult.
>
> Sorry that you went through this.
Please don't be sorry :)
Believe me when I say that I cannot explain how many things I have
learned during these days while working on this issue. I see no
problems at all but only opportunities for learning.
Thank you very much!
Fabio M. De Francesco
>
> regards,
> dan carpenter
>
>
prev parent reply other threads:[~2022-03-31 17:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 15:49 [PATCH] scsi: sd: call device_del() if device_add_disk() fails Fabio M. De Francesco
2022-03-30 4:30 ` Dan Carpenter
2022-03-31 15:26 ` Wenchao Hao
2022-03-31 5:41 ` Dan Carpenter
2022-03-31 5:45 ` Christoph Hellwig
2022-03-31 9:07 ` Fabio M. De Francesco
2022-03-31 9:13 ` Christoph Hellwig
2022-03-31 10:13 ` Fabio M. De Francesco
2022-03-31 12:14 ` Wenchao Hao
2022-03-31 13:42 ` Dan Carpenter
2022-03-31 14:19 ` James Bottomley
2022-03-31 15:11 ` Dan Carpenter
2022-03-31 16:14 ` Fabio M. De Francesco
2022-03-31 16:24 ` Dan Carpenter
2022-03-31 17:21 ` Fabio M. De Francesco [this message]
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=3427592.iIbC2pHGDl@leap \
--to=fmdefrancesco@gmail.com \
--cc=axboe@kernel.dk \
--cc=dan.carpenter@oracle.com \
--cc=haowenchao@huawei.com \
--cc=jejb@linux.ibm.com \
--cc=linfeilong@huawei.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 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).