From: Guillaume Nault <gnault@redhat.com>
To: YueHaibing <yuehaibing@huawei.com>
Cc: davem@davemloft.net, g.nault@alphalink.fr, jian.w.wen@oracle.com,
edumazet@google.com, kafai@fb.com, xiyou.wangcong@gmail.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] l2tp: Fix possible NULL pointer dereference
Date: Tue, 7 May 2019 11:23:05 +0200 [thread overview]
Message-ID: <20190507092304.GA12570@linux.home> (raw)
In-Reply-To: <20190506144404.25220-1-yuehaibing@huawei.com>
On Mon, May 06, 2019 at 10:44:04PM +0800, YueHaibing wrote:
> If alloc_workqueue fails in l2tp_init, l2tp_net_ops
> is unregistered on failure path. Then l2tp_exit_net
> is called which will flush NULL workqueue, this patch
> add a NULL check to fix it.
>
Thanks!
Acked-by: Guillaume Nault <gnault@redhat.com>
next prev parent reply other threads:[~2019-05-07 9:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 14:44 [PATCH] l2tp: Fix possible NULL pointer dereference YueHaibing
2019-05-07 9:23 ` Guillaume Nault [this message]
2019-05-07 19:17 ` David Miller
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=20190507092304.GA12570@linux.home \
--to=gnault@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=g.nault@alphalink.fr \
--cc=jian.w.wen@oracle.com \
--cc=kafai@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.com \
--cc=yuehaibing@huawei.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 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.