linux-kernel - Re: [Bug #14893] Tasks stuck on I/O on armel with 2.6.32-rc8

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: <201001052230.42567.rjw@sisk.pl>
Date:	Tue, 5 Jan 2010 22:30:42 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Daniel Kahn Gillmor <dkg@...thhorseman.net>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Kernel Testers List <kernel-testers@...r.kernel.org>
Subject: Re: [Bug #14893] Tasks stuck on I/O on armel with 2.6.32-rc8

On Tuesday 05 January 2010, Daniel Kahn Gillmor wrote:
> Hi Rafael--
> 
> On 12/29/2009 10:28 AM, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.31 and 2.6.32.
> > 
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.31 and 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=14893
> > Subject		: Tasks stuck on I/O on armel with 2.6.32-rc8
> > Submitter	: Daniel Kahn Gillmor <dkg@...thhorseman.net>
> > Date		: 2009-11-24 23:05 (36 days old)
> > References	: http://marc.info/?l=linux-kernel&m=125910438530554&w=4
> 
> The machine in question has been up continuously (though not under heavy
> load) since it was rebooted after the reported failure.  it has even
> withstood additional mpd index updates, all running the same kernel it
> crashed with before.
> 
> So i can't say that the problem is resolved, but i haven't replicated it
> either.  Wish i had more interesting details to report.

I'm going to close it as "unreprodicible", then.  Please reopen if you're able
to reproduce it after all.

> Thanks for doing followup/triage like this.

Well, you're welcome. :-)

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