All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers3@gmail.com>
To: syzbot
	<bot+25a1a3685abe943a89512250aece10bdd9aa4827@syzkaller.appspotmail.com>
Cc: davem@davemloft.net, dhowells@redhat.com,
	herbert@gondor.apana.org.au, keyrings@vger.kernel.org,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: general protection fault in strcmp
Date: Mon, 11 Dec 2017 18:55:02 +0000	[thread overview]
Message-ID: <20171211185502.GA62691@gmail.com> (raw)
In-Reply-To: <089e082676ecdedb0b055f394f11@google.com>

On Thu, Nov 30, 2017 at 12:44:01PM -0800, syzbot wrote:
> syzbot will keep track of this bug report.
> Once a fix for this bug is committed, please reply to this email with:
> #syz fix: exact-commit-title
> To mark this as a duplicate of another syzbot report, please reply with:
> #syz dup: exact-subject-of-another-report
> If it's a one-off invalid bug report, please reply with:
> #syz invalid
> Note: if the crash happens again, it will cause creation of a new
> bug report.
> Note: all commands must start from beginning of the line in the email body.
> 

#syz fix: KEYS: reject NULL restriction string when type is specified

WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers <ebiggers3@gmail.com>
To: syzbot
	<bot+25a1a3685abe943a89512250aece10bdd9aa4827@syzkaller.appspotmail.com>
Cc: davem@davemloft.net, dhowells@redhat.com,
	herbert@gondor.apana.org.au, keyrings@vger.kernel.org,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: general protection fault in strcmp
Date: Mon, 11 Dec 2017 10:55:02 -0800	[thread overview]
Message-ID: <20171211185502.GA62691@gmail.com> (raw)
In-Reply-To: <089e082676ecdedb0b055f394f11@google.com>

On Thu, Nov 30, 2017 at 12:44:01PM -0800, syzbot wrote:
> syzbot will keep track of this bug report.
> Once a fix for this bug is committed, please reply to this email with:
> #syz fix: exact-commit-title
> To mark this as a duplicate of another syzbot report, please reply with:
> #syz dup: exact-subject-of-another-report
> If it's a one-off invalid bug report, please reply with:
> #syz invalid
> Note: if the crash happens again, it will cause creation of a new
> bug report.
> Note: all commands must start from beginning of the line in the email body.
> 

#syz fix: KEYS: reject NULL restriction string when type is specified

  parent reply	other threads:[~2017-12-11 18:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <089e082676ecdedb0b055f394f11@google.com>
2017-11-30 20:51 ` [PATCH] KEYS: reject NULL restriction string when type is specified Eric Biggers
2017-11-30 20:51   ` Eric Biggers
2017-12-01  1:22   ` Mat Martineau
2017-12-01  1:22     ` Mat Martineau
2017-12-01  1:22     ` Mat Martineau
2017-12-08 14:45     ` David Howells
2017-12-08 17:52       ` Mat Martineau
2017-12-08 17:52         ` Mat Martineau
2017-12-08 17:52         ` Mat Martineau
2017-12-11 18:55 ` Eric Biggers [this message]
2017-12-11 18:55   ` general protection fault in strcmp Eric Biggers

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=20171211185502.GA62691@gmail.com \
    --to=ebiggers3@gmail.com \
    --cc=bot+25a1a3685abe943a89512250aece10bdd9aa4827@syzkaller.appspotmail.com \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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.