[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1484262618.13165.13.camel@edumazet-glaptop3.roam.corp.google.com>
Date: Thu, 12 Jan 2017 15:10:18 -0800
From: Eric Dumazet <eric.dumazet@...il.com>
To: william.c.roberts@...el.com
Cc: selinux@...ho.nsa.gov, socketcan@...tkopp.net, mkl@...gutronix.de,
davem@...emloft.net, linux-can@...r.kernel.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
sds@...ho.nsa.gov, paul@...l-moore.com,
Zhang Yanmin <yanmin.zhang@...el.com>, He@...r.kernel.org,
Bo <bo.he@...el.com>, Liu Shuo A <shuo.a.liu@...el.com>
Subject: Re: [PATCH] can: Fix kernel panic at security_sock_rcv_skb
On Thu, 2017-01-12 at 14:40 -0800, william.c.roberts@...el.com wrote:
> From: Zhang Yanmin <yanmin.zhang@...el.com>
>
> The patch is for fix the below kernel panic:
> BUG: unable to handle kernel NULL pointer dereference at (null)
> IP: [<ffffffff81495e25>] selinux_socket_sock_rcv_skb+0x65/0x2a0
Same patch was sent earlier, and we gave a feedback on it.
Adding synchronize_rcu() calls is a step backward.
https://patchwork.ozlabs.org/patch/714446/
Powered by blists - more mailing lists