From: Arvind Yadav <arvind.yadav.cs@gmail.com>
To: Richard Weinberger <richard@nod.at>
Cc: dwmw2@infradead.org, computersforpeace@gmail.com,
boris.brezillon@free-electrons.com, marek.vasut@gmail.com,
cyrille.pitchen@wedev4u.fr, dedekind1@gmail.com,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org
Subject: Re: [PATCH 2/2 v2] mtd: ubi: use put_device() if device_register fail
Date: Thu, 15 Mar 2018 14:17:25 +0530 [thread overview]
Message-ID: <11250cfc-f092-b299-1044-50334c518bf1@gmail.com> (raw)
In-Reply-To: <5296799.FRhcbj8Hd9@blindfold>
On Thursday 15 March 2018 01:25 PM, Richard Weinberger wrote:
> Am Donnerstag, 15. März 2018, 08:20:31 CET schrieb Arvind Yadav:
>> if device_register() returned an error! Always use put_device()
>> to give up the reference initialized.
> Like DaveM said, there is no need to shout and use "!".
I will fix this and send you update patch.
>
>> Signed-off-by: Arvind Yadav <arvind.yadav.cs@gmail.com>
>> ---
>> change in v2:
>> Fix use-after-free bug. move put_device() after cdev_del().
>>
>> drivers/mtd/ubi/vmt.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/mtd/ubi/vmt.c b/drivers/mtd/ubi/vmt.c
>> index 3fd8d7f..93c6163 100644
>> --- a/drivers/mtd/ubi/vmt.c
>> +++ b/drivers/mtd/ubi/vmt.c
>> @@ -610,6 +610,7 @@ int ubi_add_volume(struct ubi_device *ubi, struct
>> ubi_volume *vol)
>>
>> out_cdev:
>> cdev_del(&vol->cdev);
>> + put_device(&vol->dev);
>> return err;
> The more I dig into device code, the more questions I have.
> Why is cdev_del() not part of the release function?
>
> Thanks,
> //richard
Yes, It's should be a part release function.
~arvind
next prev parent reply other threads:[~2018-03-15 8:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 7:20 Arvind Yadav
2018-03-15 7:55 ` Richard Weinberger
2018-03-15 8:47 ` Arvind Yadav [this message]
2018-03-15 17:41 ` arvindY
2018-03-16 7:50 ` Richard Weinberger
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=11250cfc-f092-b299-1044-50334c518bf1@gmail.com \
--to=arvind.yadav.cs@gmail.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=richard@nod.at \
/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
all inboxes | Powered by JetHome®