[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220331134210.GF12805@kadam>
Date: Thu, 31 Mar 2022 16:42:10 +0300
From: Dan Carpenter <dan.carpenter@...cle.com>
To: Wenchao Hao <haowenchao@...wei.com>,
syzkaller-bugs@...glegroups.com
Cc: fmdefrancesco@...il.com, axboe@...nel.dk, jejb@...ux.ibm.com,
linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-scsi@...r.kernel.org, martin.petersen@...cle.com,
syzbot+f08c77040fa163a75a46@...kaller.appspotmail.com,
syzkaller-bugs@...glegroups.com, linfeilong@...wei.com
Subject: Re: [PATCH] scsi: sd: call device_del() if device_add_disk() fails
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?
This is another reason why syzbot should display the whole dmesg because
otherwise we can't ask people link to their test results if it just says
"PASSED" with no additional information. If syzbot provided a dmesg
at the end then I would require a link to it under the --- cut off
line for patches that I review.
In a way this gets back to the original testing that syzbot did do. If
Wenchao's reading of the code is correct the Fabio's patch caused a
series of use after free bugs but because the test results just said
"PASSED" with no additional information.
Either way, failing to call device_del() is still a bug.
Also, I don't really understand why we don't have to call
put_device(&sdkp->disk_dev) at the end of sd_remove().
regards,
dan carpenter
Powered by blists - more mailing lists