From: Greg KH <gregkh@suse.de>
To: 최종환 <jhbird.choi@samsung.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
김국진 <kgene.kim@samsung.com>
Subject: Re: Re: [PATCH] driver-core: Fix null reference in subsys_interface_unregister
Date: Mon, 16 Jan 2012 16:59:44 -0800 [thread overview]
Message-ID: <20120117005944.GA14863@suse.de> (raw)
In-Reply-To: <15905052.41411326760535818.JavaMail.weblogic@epv6ml08>
On Tue, Jan 17, 2012 at 12:35:35AM +0000, 최종환 wrote:
> Greg KH wrote:
>
> >On Sat, Jan 14, 2012 at 11:06:03AM +0900, jhbird.choi@samsung.com wrote:
> >> From: Jonghwan Choi
> > >
> > >Check if the sif is not NULL before de-referencing it
>
> >Why would it be? Have you hit this somehow? If so, in what code?
>
> > thanks,
>
> > greg k-h
>
>
> diff --git a/drivers/base/bus.c b/drivers/base/bus.c
> index 99dc592..4ddb38b 100644
> --- a/drivers/base/bus.c
> +++ b/drivers/base/bus.c
> @@ -1193,13 +1193,15 @@ EXPORT_SYMBOL_GPL(subsys_interface_register);
>
> void subsys_interface_unregister(struct subsys_interface *sif)
> {
> - struct bus_type *subsys = sif->subsys; // -> Sif is already used, that means sif is not null
> + struct bus_type *subsys;
> struct subsys_dev_iter iter;
> struct device *dev;
>
> - if (!sif) // -> Check whether sif is null
> + if (!sif || !sif->subsys)
> return;
>
> + subsys = sif->subsys;
> +
> mutex_lock(&subsys->p->mutex);
> list_del_init(&sif->node);
> if (sif->remove_dev) {
> --
>
> sif is already used, but null pointer check for sif later.
> so i think that sif should be checked before use it.
Yes, you are right, I missed the previous usage. I'll queue this up for
3.4.
thanks,
greg k-h
prev parent reply other threads:[~2012-01-17 1:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 0:35 Re: [PATCH] driver-core: Fix null reference in subsys_interface_unregister 최종환
2012-01-17 0:59 ` Greg KH [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=20120117005944.GA14863@suse.de \
--to=gregkh@suse.de \
--cc=jhbird.choi@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.