All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Vyukov <dvyukov@google.com>
To: David Howells <dhowells@redhat.com>
Cc: syzbot <syzbot+6455648abc28dbdd1e7f@syzkaller.appspotmail.com>,
	Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
	James Morris <jmorris@namei.org>,
	keyrings@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	linux-security-module <linux-security-module@vger.kernel.org>,
	"Serge E. Hallyn" <serge@hallyn.com>,
	syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: WARNING: refcount bug in find_key_to_update
Date: Mon, 21 Oct 2019 16:05:41 +0000	[thread overview]
Message-ID: <CACT4Y+ZZ2tmUg9PAKouK5zhNw=BDWD7+jfo_JjB92Eb+g_gAQQ@mail.gmail.com> (raw)
In-Reply-To: <8509.1571673553@warthog.procyon.org.uk>

On Mon, Oct 21, 2019 at 5:59 PM David Howells <dhowells@redhat.com> wrote:
>
> syzbot <syzbot+6455648abc28dbdd1e7f@syzkaller.appspotmail.com> wrote:
>
> > syz repro:      https://syzkaller.appspot.com/x/repro.syz?x\x11c8adab600000
>
> 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.

WARNING: multiple messages have this Message-ID (diff)
From: Dmitry Vyukov <dvyukov@google.com>
To: David Howells <dhowells@redhat.com>
Cc: syzbot <syzbot+6455648abc28dbdd1e7f@syzkaller.appspotmail.com>,
	Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
	James Morris <jmorris@namei.org>,
	keyrings@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	linux-security-module <linux-security-module@vger.kernel.org>,
	"Serge E. Hallyn" <serge@hallyn.com>,
	syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: WARNING: refcount bug in find_key_to_update
Date: Mon, 21 Oct 2019 18:05:41 +0200	[thread overview]
Message-ID: <CACT4Y+ZZ2tmUg9PAKouK5zhNw=BDWD7+jfo_JjB92Eb+g_gAQQ@mail.gmail.com> (raw)
In-Reply-To: <8509.1571673553@warthog.procyon.org.uk>

On Mon, Oct 21, 2019 at 5:59 PM David Howells <dhowells@redhat.com> wrote:
>
> syzbot <syzbot+6455648abc28dbdd1e7f@syzkaller.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.

  reply	other threads:[~2019-10-21 16:05 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-17  1:42 WARNING: refcount bug in find_key_to_update syzbot
2019-10-17  1:42 ` syzbot
2019-10-17  2:42 ` syzbot
2019-10-17  2:42   ` syzbot
2019-10-17  2:42   ` syzbot
2019-10-17 15:53   ` Linus Torvalds
2019-10-17 15:53     ` Linus Torvalds
2019-10-17 15:53     ` Linus Torvalds
2019-10-17 16:00     ` Eric Biggers
2019-10-17 16:00       ` Eric Biggers
2019-10-17 16:00       ` Eric Biggers
2019-10-18 10:54       ` Tetsuo Handa
2019-10-18 10:54         ` Tetsuo Handa
2019-10-18 16:45       ` David Howells
2019-10-18 16:45         ` David Howells
2019-10-18 16:38   ` David Howells
2019-10-18 16:38     ` David Howells
2019-10-18 16:38     ` David Howells
2019-10-22 10:35   ` David Howells
2019-10-22 10:35     ` David Howells
2019-10-22 10:35     ` David Howells
2019-10-22 13:17   ` David Howells
2019-10-22 13:17     ` David Howells
2019-10-22 13:17     ` David Howells
2019-10-21 15:59 ` David Howells
2019-10-21 15:59   ` David Howells
2019-10-21 16:05   ` Dmitry Vyukov [this message]
2019-10-21 16:05     ` Dmitry Vyukov
     [not found] <20191017092428.7336-1-hdanton@sina.com>
2019-10-18 16:46 ` David Howells
2019-10-18 16:46   ` David Howells

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='CACT4Y+ZZ2tmUg9PAKouK5zhNw=BDWD7+jfo_JjB92Eb+g_gAQQ@mail.gmail.com' \
    --to=dvyukov@google.com \
    --cc=dhowells@redhat.com \
    --cc=jarkko.sakkinen@linux.intel.com \
    --cc=jmorris@namei.org \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=serge@hallyn.com \
    --cc=syzbot+6455648abc28dbdd1e7f@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.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.