From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Biggers Date: Fri, 1 Dec 2017 11:21:52 -0800 Subject: [LTP] 3239b6f29b ("KEYS: return full count in keyring_read() if buffer is too small"): ltp.keyctl06.fail In-Reply-To: <20171201024012.wsq3xnsbbdqwxwp2@wfg-t540p.sh.intel.com> References: <20171201024012.wsq3xnsbbdqwxwp2@wfg-t540p.sh.intel.com> Message-ID: <20171201192152.GD142348@google.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ltp@lists.linux.it 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============6592031692520432111==" MIME-Version: 1.0 From: Eric Biggers 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 Message-ID: <20171201192152.GD142348@google.com> In-Reply-To: <20171201024012.wsq3xnsbbdqwxwp2@wfg-t540p.sh.intel.com> List-Id: --===============6592031692520432111== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable 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 coun= t 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 wit= h 64G memory > with following parameters: > = > disk: 1HDD > fs: ext4 > test: syscalls_part2 > = > test-description: The LTP testsuite contains a collection of tools for te= sting 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 tes= t for follow-on fix")? It would be really helpful if these reports would include= the LTP commit that was used. Eric --===============6592031692520432111==-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752166AbdLATXS (ORCPT ); Fri, 1 Dec 2017 14:23:18 -0500 Received: from mail-io0-f177.google.com ([209.85.223.177]:42012 "EHLO mail-io0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751772AbdLATV5 (ORCPT ); Fri, 1 Dec 2017 14:21:57 -0500 X-Google-Smtp-Source: AGs4zMbqwmdhPezqAHUBxOii0I52hGmS/Uuwkh2YzHV4Dk2jec5mYOipB3umCOFw4kXujOAhRz54Iw== Date: Fri, 1 Dec 2017 11:21:52 -0800 From: Eric Biggers To: Fengguang Wu Cc: James Morris , Ben Hutchings , David Howells , LKML , Linus Torvalds , 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 Message-ID: <20171201192152.GD142348@google.com> References: <20171201024012.wsq3xnsbbdqwxwp2@wfg-t540p.sh.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171201024012.wsq3xnsbbdqwxwp2@wfg-t540p.sh.intel.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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