[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACT4Y+ZZ2tmUg9PAKouK5zhNw=BDWD7+jfo_JjB92Eb+g_gAQQ@mail.gmail.com>
Date: Mon, 21 Oct 2019 18:05:41 +0200
From: Dmitry Vyukov <dvyukov@...gle.com>
To: David Howells <dhowells@...hat.com>
Cc: syzbot <syzbot+6455648abc28dbdd1e7f@...kaller.appspotmail.com>,
Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>,
James Morris <jmorris@...ei.org>, keyrings@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>,
linux-security-module <linux-security-module@...r.kernel.org>,
"Serge E. Hallyn" <serge@...lyn.com>,
syzkaller-bugs <syzkaller-bugs@...glegroups.com>
Subject: Re: WARNING: refcount bug in find_key_to_update
On Mon, Oct 21, 2019 at 5:59 PM David Howells <dhowells@...hat.com> wrote:
>
> syzbot <syzbot+6455648abc28dbdd1e7f@...kaller.appspotmail.com> wrote:
>
> > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11c8adab600000
>
> How do I tell what's been passed into the add_key for the encrypted key?
Hi David,
The easiest and most reliable would be to run it and dump the data in
the kernel function.
Powered by blists - more mailing lists