From: David Howells <dhowells@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] kernel of next-20170602 call trace when run add_key02 in LTP
Date: Tue, 06 Jun 2017 10:40:12 +0100 [thread overview]
Message-ID: <25659.1496742012@warthog.procyon.org.uk> (raw)
In-Reply-To: <20170605172855.GA87699@gmail.com>
Eric Biggers <ebiggers3@gmail.com> wrote:
> David, can you get keys-next up to date with keys-fixes so that people
> don't run into this bug? Note that it was also hit with the Trinity fuzzer.
Done.
David
prev parent reply other threads:[~2017-06-06 9:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACsHhCKXwfo3hn3uNwQUWTg-MS9Ja5_5USO--Df3kRi2Z0b-hg@mail.gmail.com>
2017-06-05 13:48 ` [LTP] kernel of next-20170602 call trace when run add_key02 in LTP Cyril Hrubis
2017-06-05 17:28 ` Eric Biggers
2017-06-06 9:40 ` David Howells [this message]
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=25659.1496742012@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=ltp@lists.linux.it \
/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