From: Richard Palethorpe <rpalethorpe@suse.de>
To: Eric Biggers <ebiggers@google.com>
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, 05 Dec 2017 10:43:08 +0100 [thread overview]
Message-ID: <87a7yxmrwz.fsf@rpws.prws.suse.cz> (raw)
In-Reply-To: <20171201192152.GD142348@google.com>
Hello,
Eric Biggers writes:
> On Fri, Dec 01, 2017 at 10:40:12AM +0800, Fengguang Wu wrote:
>> Hi Eric,
>>
>> We noticed LTP keyctl06 test regression in
>>
>> commit: 3239b6f29bdfb4b0a2ba59df995fc9e6f4df7f1f ("KEYS: return full count in keyring_read() if buffer is too small")
>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
>>
>> on test machine: 48 threads Intel(R) Xeon(R) CPU E5-2697 v2 @ 2.70GHz with 64G memory
>> with following parameters:
>>
>> disk: 1HDD
>> fs: ext4
>> test: syscalls_part2
>>
>> test-description: The LTP testsuite contains a collection of tools for testing the Linux kernel and related features.
>> test-url: http://linux-test-project.github.io/
>>
>> To reproduce:
>>
>> git clone https://github.com/intel/lkp-tests.git
>> cd lkp-tests
>> bin/lkp install job.yaml # job file is attached in this email
>> bin/lkp run job.yaml
>>
>> testcase/path_params/tbox_group/run: ltp/1HDD-ext4-syscalls_part2/ivb44
>>
>
> Did this include LTP commit f21703fe45d3 ("syscalls/keyctl06: update to test for
> follow-on fix")? It would be really helpful if these reports would include the
> LTP commit that was used.
>
> Eric
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.
--
Thank you,
Richard.
next prev parent reply other threads:[~2017-12-05 9:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 2:40 Fengguang Wu
2017-12-01 19:21 ` Eric Biggers
2017-12-05 9:43 ` Richard Palethorpe [this message]
2017-12-05 18:10 ` [LTP] " 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=87a7yxmrwz.fsf@rpws.prws.suse.cz \
--to=rpalethorpe@suse.de \
--cc=ben@decadent.org.uk \
--cc=dhowells@redhat.com \
--cc=ebiggers@google.com \
--cc=fengguang.wu@intel.com \
--cc=james.l.morris@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=ltp@lists.linux.it \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®