Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Tue, 27 Apr 2021 15:01:22 +0200
From:   Greg KH <gregkh@linuxfoundation.org>
To:     Jens Axboe <axboe@kernel.dk>
Cc:     Peter Rosin <peda@axentia.se>, linux-kernel@vger.kernel.org,
        wang6495@umn.edu
Subject: Re: [PATCH 167/190] Revert "gdrom: fix a memory leak bug"
Message-ID: <YIgLIscB1I8MxkWP@kroah.com>
References: <20210421130105.1226686-168-gregkh@linuxfoundation.org>
 <23ffd3c5-0095-6a95-8c30-2b6f67377ce7@axentia.se>
 <14bdfbee-b8b9-d8ac-de34-b6d852d1485b@kernel.dk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <14bdfbee-b8b9-d8ac-de34-b6d852d1485b@kernel.dk>
Precedence: bulk

On Fri, Apr 23, 2021 at 08:20:30AM -0600, Jens Axboe wrote:
> On 4/22/21 3:29 PM, Peter Rosin wrote:
> >> This reverts commit 093c48213ee37c3c3ff1cf5ac1aa2a9d8bc66017.
> > 
> > The reverted patch looks fishy.
> > 
> > gc.cd_info is kzalloc:ed on probe. In case probe fails after this allocation, the
> > memory is kfree:d but the variable is NOT zeroed out.
> > 
> > AFAICT, the above leads to a double-free on exit by the added line.
> > 
> > I believe gd.cd_info should be kfree:d on remove instead.
> > 
> > However, might not gc.toc also be kfree:d twice for similar reasons?
> > 
> > I could easily be mistaken.
> 
> >From taking a quick look the other day, that's my conclusion too. I
> don't think the patch is correct, but I don't think the surrounding code
> is correct right now either.

Thanks for the review from both of you, I'll keep this commit in the
tree.

greg k-h