From: Sachin Sant <sachinp@linux.vnet.ibm.com>
To: Hillf Danton <hdanton@sina.com>
Cc: dhowells@redhat.com, linuxppc-dev@ozlabs.org,
keyrings@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Oops (request_key_auth_describe) while running cve-2016-7042 from LTP
Date: Fri, 30 Aug 2019 16:02:03 +0530 [thread overview]
Message-ID: <C41D3A16-835C-421C-9059-AABB7273E664@linux.vnet.ibm.com> (raw)
In-Reply-To: <20190830085646.14740-1-hdanton@sina.com>
> On 30-Aug-2019, at 2:26 PM, Hillf Danton <hdanton@sina.com> wrote:
>
>
> On Fri, 30 Aug 2019 12:18:07 +0530 Sachin Sant wrote:
>>
>> [ 8074.351033] BUG: Kernel NULL pointer dereference at 0x00000038
>> [ 8074.351046] Faulting instruction address: 0xc0000000004ddf30
>> [ 8074.351052] Oops: Kernel access of bad area, sig: 11 [#1]
>> [ 8074.351056] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA pSeries
>
> Add rcu gp.
>
> --- a/security/keys/request_key_auth.c
> +++ b/security/keys/request_key_auth.c
> @@ -64,12 +64,19 @@ static int request_key_auth_instantiate(
> static void request_key_auth_describe(const struct key *key,
> struct seq_file *m)
> {
> - struct request_key_auth *rka = dereference_key_rcu(key);
> + struct request_key_auth *rka;
> +
> + rcu_read_lock();
> + rka = dereference_key_rcu(key);
> + if (!rka)
> + goto out;
>
Thanks for the patch. Works for me. Test ran fine without any problems.
Tested-by: Sachin Sant <sachinp@linux.vnet.ibm.com>
Thanks
-Sachin
next prev parent reply other threads:[~2019-08-30 10:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190830145454.B91DF125411@zmta02.collab.prod.int.phx2.redhat.com>
2019-08-30 8:56 ` Oops (request_key_auth_describe) while running cve-2016-7042 from LTP Hillf Danton
2019-08-30 10:32 ` Sachin Sant [this message]
2019-08-30 14:13 ` David Howells
2019-08-30 14:54 ` Hillf Danton
2019-08-30 15:12 ` David Howells
2019-08-31 1:20 ` Hillf Danton
2019-08-30 6:48 Sachin Sant
2019-08-30 15:13 ` David Howells
2019-08-31 4:57 ` Sachin Sant
2019-09-02 7:14 ` David Howells
2019-09-02 11:40 ` Hillf Danton
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=C41D3A16-835C-421C-9059-AABB7273E664@linux.vnet.ibm.com \
--to=sachinp@linux.vnet.ibm.com \
--cc=dhowells@redhat.com \
--cc=hdanton@sina.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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 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).