From: David Miller <davem@davemloft.net>
To: xiaolou4617@gmail.com
Cc: andrew.hendry@gmail.com, linux-x25@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v3] net: x25: fix one potential use-after-free issue
Date: Thu, 18 May 2017 10:06:08 -0400 (EDT) [thread overview]
Message-ID: <20170518.100608.733334484371439292.davem@davemloft.net> (raw)
In-Reply-To: <1494993907-22727-1-git-send-email-xiaolou4617@gmail.com>
From: linzhang <xiaolou4617@gmail.com>
Date: Wed, 17 May 2017 12:05:07 +0800
> The function x25_init is not properly unregister related resources
> on error handler.It is will result in kernel oops if x25_init init
> failed, so add properly unregister call on error handler.
>
> Also, i adjust the coding style and make x25_register_sysctl properly
> return failure.
>
> Signed-off-by: linzhang <xiaolou4617@gmail.com>
Applied, thanks.
prev parent reply other threads:[~2017-05-18 14:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 4:05 [PATCH net v3] net: x25: fix one potential use-after-free issue linzhang
2017-05-18 14:06 ` David Miller [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=20170518.100608.733334484371439292.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew.hendry@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-x25@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=xiaolou4617@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).