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] [thread-next>] [day] [month] [year] [list]
Message-ID: <1263428136.29868.5058.camel@calx>
Date:	Wed, 13 Jan 2010 18:15:36 -0600
From:	Matt Mackall <mpm@...enic.com>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	Américo Wang <xiyou.wangcong@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Kernel Testers List <kernel-testers@...r.kernel.org>
Subject: Re: [Bug #15041] Pagemap endless read loop with LTP

On Thu, 2010-01-14 at 00:50 +0100, Andi Kleen wrote:
> On Wed, Jan 13, 2010 at 10:57:34PM +0100, Rafael J. Wysocki wrote:
> > On Wednesday 13 January 2010, Américo Wang wrote:
> > > On Mon, Jan 11, 2010 at 6:32 AM, Rafael J. Wysocki <rjw@...k.pl> wrote:
> > > > This message has been generated automatically as a part of a report
> > > > of recent regressions.
> > > >
> > > > The following bug entry is on the current list of known regressions
> > > > from 2.6.32.  Please verify if it still should be listed and let me know
> > > > (either way).
> > > >
> > > >
> > > > Bug-Entry       : http://bugzilla.kernel.org/show_bug.cgi?id=15041
> > > > Subject         : Pagemap endless read loop with LTP
> > > > Submitter       : Andi Kleen <andi@...stfloor.org>
> > > > Date            : 2010-01-10 2:09 (1 days old)
> > > > References      : http://marc.info/?l=linux-kernel&m=126308941423848&w=4
> > > >
> > > 
> > > According to Andi's later reply, it shoud not be an endless loop,
> > > it just takes a rather long time.
> > 
> > Andi?
> 
> It'll try to read 47 bits worth of 0s on 64bit x86-64. 
> 
> I haven't tried to wait until that finishes, but I estimate a few months of 
> CPU time at least.
> 
> The interface is just misdesigned, but I guess we cannot do
> anything about that for now.

It's perfectly sensible. What's not sensible is reading the entirety of
everything you find in /proc, something that just about every Linux
admin figures out moments after running their first recursive grep.

>  LTP will just need to do a workaround.

Or they could actually, you know, add a test of pagemap. Not much chance
of that, though - CVS reports it took them until 2005 to figure out that
skipping /proc/kcore was a good idea.

-- 
http://selenic.com : development and support for Mercurial and Linux


--
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