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: Fri, 1 Dec 2017 11:21:52 -0800 [thread overview]
Message-ID: <20171201192152.GD142348@google.com> (raw)
In-Reply-To: <20171201024012.wsq3xnsbbdqwxwp2@wfg-t540p.sh.intel.com>
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
WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers <ebiggers@google.com>
To: lkp@lists.01.org
Subject: Re: 3239b6f29b ("KEYS: return full count in keyring_read() if buffer is too small"): ltp.keyctl06.fail
Date: Fri, 01 Dec 2017 11:21:52 -0800 [thread overview]
Message-ID: <20171201192152.GD142348@google.com> (raw)
In-Reply-To: <20171201024012.wsq3xnsbbdqwxwp2@wfg-t540p.sh.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1185 bytes --]
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
WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers <ebiggers@google.com>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: James Morris <james.l.morris@oracle.com>,
Ben Hutchings <ben@decadent.org.uk>,
David Howells <dhowells@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
lkp@01.org, ltp@lists.linux.it
Subject: Re: 3239b6f29b ("KEYS: return full count in keyring_read() if buffer is too small"): ltp.keyctl06.fail
Date: Fri, 1 Dec 2017 11:21:52 -0800 [thread overview]
Message-ID: <20171201192152.GD142348@google.com> (raw)
In-Reply-To: <20171201024012.wsq3xnsbbdqwxwp2@wfg-t540p.sh.intel.com>
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
next prev parent reply other threads:[~2017-12-01 19:21 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 ` Eric Biggers [this message]
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
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=20171201192152.GD142348@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.