linux-kernel - Re: [PATCH] l2tp: Fix possible NULL pointer dereference

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20190507092304.GA12570@linux.home>
Date:   Tue, 7 May 2019 11:23:05 +0200
From:   Guillaume Nault <gnault@...hat.com>
To:     YueHaibing <yuehaibing@...wei.com>
Cc:     davem@...emloft.net, g.nault@...halink.fr, jian.w.wen@...cle.com,
        edumazet@...gle.com, kafai@...com, xiyou.wangcong@...il.com,
        linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH] l2tp: Fix possible NULL pointer dereference

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@...hat.com>