From: Eric Biggers <ebiggers@google.com>
To: ltp@lists.linux.it
Subject: [LTP] 3239b6f29b ("KEYS: return full count in keyring_read() if buffer is too small"): ltp.keyctl06.fail
Date: Tue, 5 Dec 2017 10:10:47 -0800 [thread overview]
Message-ID: <20171205181047.GA66710@google.com> (raw)
In-Reply-To: <87a7yxmrwz.fsf@rpws.prws.suse.cz>
On Tue, Dec 05, 2017 at 10:43:08AM +0100, Richard Palethorpe wrote:
>
> We are getting the following result, even with the follow up patch:
>
> keyctl06.c:68: FAIL: KEYCTL_READ returned 4 but expected 8
>
> This is with SUSE SLE15 kernel 4.12.14. I haven't had chance to
> investigate it yet.
>
Does the kernel include *both* fixes the test tests for now?
WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers <ebiggers@google.com>
To: lkp@lists.01.org
Subject: Re: [LTP] 3239b6f29b ("KEYS: return full count in keyring_read() if buffer is too small"): ltp.keyctl06.fail
Date: Tue, 05 Dec 2017 10:10:47 -0800 [thread overview]
Message-ID: <20171205181047.GA66710@google.com> (raw)
In-Reply-To: <87a7yxmrwz.fsf@rpws.prws.suse.cz>
[-- Attachment #1: Type: text/plain, Size: 372 bytes --]
On Tue, Dec 05, 2017 at 10:43:08AM +0100, Richard Palethorpe wrote:
>
> We are getting the following result, even with the follow up patch:
>
> keyctl06.c:68: FAIL: KEYCTL_READ returned 4 but expected 8
>
> This is with SUSE SLE15 kernel 4.12.14. I haven't had chance to
> investigate it yet.
>
Does the kernel include *both* fixes the test tests for now?
WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers <ebiggers@google.com>
To: Richard Palethorpe <rpalethorpe@suse.de>
Cc: Fengguang Wu <fengguang.wu@intel.com>,
Ben Hutchings <ben@decadent.org.uk>,
LKML <linux-kernel@vger.kernel.org>,
David Howells <dhowells@redhat.com>,
lkp@01.org, James Morris <james.l.morris@oracle.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
ltp@lists.linux.it
Subject: Re: [LTP] 3239b6f29b ("KEYS: return full count in keyring_read() if buffer is too small"): ltp.keyctl06.fail
Date: Tue, 5 Dec 2017 10:10:47 -0800 [thread overview]
Message-ID: <20171205181047.GA66710@google.com> (raw)
In-Reply-To: <87a7yxmrwz.fsf@rpws.prws.suse.cz>
On Tue, Dec 05, 2017 at 10:43:08AM +0100, Richard Palethorpe wrote:
>
> We are getting the following result, even with the follow up patch:
>
> keyctl06.c:68: FAIL: KEYCTL_READ returned 4 but expected 8
>
> This is with SUSE SLE15 kernel 4.12.14. I haven't had chance to
> investigate it yet.
>
Does the kernel include *both* fixes the test tests for now?
next prev parent reply other threads:[~2017-12-05 18:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 2:40 3239b6f29b ("KEYS: return full count in keyring_read() if buffer is too small"): ltp.keyctl06.fail Fengguang Wu
2017-12-01 2:40 ` Fengguang Wu
2017-12-01 19:21 ` [LTP] " Eric Biggers
2017-12-01 19:21 ` Eric Biggers
2017-12-01 19:21 ` Eric Biggers
2017-12-05 9:43 ` [LTP] " Richard Palethorpe
2017-12-05 9:43 ` Richard Palethorpe
2017-12-05 9:43 ` Richard Palethorpe
2017-12-05 18:10 ` Eric Biggers [this message]
2017-12-05 18:10 ` Eric Biggers
2017-12-05 18:10 ` 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=20171205181047.GA66710@google.com \
--to=ebiggers@google.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 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.