lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Tue, 24 Nov 2015 11:03:41 +0100
From:	Jan Kara <jack@...e.cz>
To:	"Huang, Ying" <ying.huang@...el.com>
Cc:	Jan Kara <jack@...e.cz>, Avi Kivity <avi@...lladb.com>,
	LKML <linux-kernel@...r.kernel.org>,
	0day robot <fengguang.wu@...el.com>, lkp@...org,
	Steven Whitehouse <swhiteho@...hat.com>
Subject: Re: [LKP] [lkp] [direct] e594571852: xfstests.generic.299.fail

On Tue 24-11-15 12:45:54, Huang, Ying wrote:
> Jan Kara <jack@...e.cz> writes:
> 
> >   Hello,
> >
> > On Mon 23-11-15 16:29:25, kernel test robot wrote:
> >> FYI, we noticed the below changes on
> >> 
> >> git://internal_merge_and_test_tree
> >> revert-e594571852b03a5503ba48edd718462e99bf238e-e594571852b03a5503ba48edd718462e99bf238e
> >> commit e594571852b03a5503ba48edd718462e99bf238e ("direct-io: Fix negative return from dio read beyond eof")
> >
> > Do you have the file:
> >
> > /lkp/benchmarks/xfstests/results//generic/299.full
> >
> > produced by the failed test? Thanks!
> 
> I found we have this feature in our test scripts already, just need to
> fix a bug in script, but that is just done yesterday!  Please check the
> 299.full attached.

Thanks for the file. The cause of failure is ENOMEM error aio-dio-verifier
got - so it is very likely unrelated to my patch:

fio: io_u.c:1315: __get_io_u: Assertion `io_u->flags & IO_U_F_FREE' failed.
fio: pid=607, got signal=6
fio: io_u error on file /fs/scratch/aio-dio-verifier: Cannot allocate memory
     read offset=8446353408, buflen=4096
fio: io_u error on file /fs/scratch/aio-dio-verifier: Cannot allocate memory
     read offset=71839776768, buflen=4096
aio-dio-verifier: (groupid=0, jobs=1): err=12 (file:io_u.c:1548, func=io_u
  error, error=Cannot allocate memory): pid=605: Tue Nov 24 11:18:39 2015
  cpu          : usr=0.00%, sys=0.10%, ctx=42, majf=0, minf=14
  IO depths    : 1=0.8%, 2=1.6%, 4=3.1%, 8=6.2%, 16=12.5%, 32=25.0%, >=64=50.8%
     submit    : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
     complete  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
     issued    : total=r=64/w=64/d=0, short=r=0/w=0/d=0
     errors    : total=0, first_error=0/<Success>
     latency   : target=0, window=0, percentile=100.00%, depth=128

If you have time, you can check why ENOMEM actually happens in your test
setup...

								Honza
-- 
Jan Kara <jack@...e.com>
SUSE Labs, CR
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ