[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YkKvZ1bp0Q5bi2ln@infradead.org>
Date: Tue, 29 Mar 2022 00:04:07 -0700
From: Christoph Hellwig <hch@...radead.org>
To: "Fabio M. De Francesco" <fmdefrancesco@...il.com>
Cc: Dan Carpenter <dan.carpenter@...cle.com>, axboe@...nel.dk,
linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
syzkaller-bugs@...glegroups.com,
"James E.J. Bottomley" <jejb@...ux.ibm.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
linux-scsi@...r.kernel.org,
syzbot+f08c77040fa163a75a46@...kaller.appspotmail.com
Subject: Re: [PATCH] scsi: sd: Jump to out_free_index if device_add{,_disk}()
fail
On Tue, Mar 29, 2022 at 08:18:16AM +0200, Fabio M. De Francesco wrote:
> Yes, correct. I've just looked at how put_device() is implemented. I didn't
> know how it works until you made me notice. Thanks!
>
> Aside this I sent another diff to Syzbot. Today, at 4.30 CET, it replied again
> that, after applying and testing my new patch, Syzkaller was not anymore able
> to trigger the memory leak that it had reported.
>
> This is the new diff...
Yes, this new diff makes much more sense.
Powered by blists - more mailing lists