linux-kernel - Re: [Bug #13899] Oops from tar, 2.6.31-rc5, 32 bit on quad core phenom.

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: <200908101607.55673.rjw@sisk.pl>
Date:	Mon, 10 Aug 2009 16:07:55 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Gene Heskett <gene.heskett@...izon.net>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Kernel Testers List <kernel-testers@...r.kernel.org>
Subject: Re: [Bug #13899] Oops from tar, 2.6.31-rc5, 32 bit on quad core phenom.

On Monday 10 August 2009, Gene Heskett wrote:
> On Sunday 09 August 2009, Rafael J. Wysocki 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.30.  Please verify if it still should be listed and let me know
> >(either way).
> >
> >
> >Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=13899
> >Subject		: Oops from tar, 2.6.31-rc5, 32 bit on quad core phenom.
> >Submitter	: Gene Heskett <gene.heskett@...izon.net>
> >Date		: 2009-08-01 13:04 (9 days old)
> >References	: http://marc.info/?l=linux-kernel&m=124913190304149&w=4
> 
> Yes, it is still doing it to rc5 but only on the first invocation after the 
> bootup.  Strangely, it apparently has no other effect, either on the machine, 
> or how amanda itself works.

Thanks for the update.

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/