From: Myungho Jung <mhjungk@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: edumazet@google.com, netdev@vger.kernel.org
Subject: Re: [PATCH v2] net: core: Prevent from dereferencing null pointer when
Date: Mon, 24 Apr 2017 18:00:52 -0700 [thread overview]
Message-ID: <20170425010052.GA8717@fqdn.specialj.com> (raw)
In-Reply-To: <20170424.120235.438297438450788048.davem@davemloft.net>
On Mon, Apr 24, 2017 at 12:02:35PM -0400, David Miller wrote:
> From: Myungho Jung <mhjungk@gmail.com>
> Date: Thu, 20 Apr 2017 16:59:20 -0700
>
> > Added NULL check to make __dev_kfree_skb_irq consistent with kfree
> > family of functions.
> >
> > Link: https://bugzilla.kernel.org/show_bug.cgi?id=195289
> >
> > Signed-off-by: Myungho Jung <mhjungk@gmail.com>
> > ---
> > Changes in v2:
> > - Correct category in subject
>
> This subject line is an incomplete sentence.
>
> This patch prevents dereferenccing a null pointer when "what"?
As it was reported on bugzilla, it would happen when plugging p54 usb device
to RPi2. But, i'm not 100% sure that this patch will resolve the issue because
the reporter didn't try my patch yet and I don't have the device to test.
And there might be some other places calling the function without checking
null pointer. The thing is that only the function don't check null among
kfree functions. So, I just hope this patch will prevent potential oops
issues.
Thanks,
Myungho
next prev parent reply other threads:[~2017-04-25 1:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 23:59 [PATCH v2] net: core: Prevent from dereferencing null pointer when Myungho Jung
2017-04-24 16:02 ` David Miller
2017-04-25 1:00 ` Myungho Jung [this message]
2017-04-25 1:10 ` Eric Dumazet
2017-04-25 1:36 ` Myungho Jung
2017-04-25 1:44 ` David Miller
2017-04-25 2:39 ` Myungho Jung
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=20170425010052.GA8717@fqdn.specialj.com \
--to=mhjungk@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=netdev@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.