linux-kernel - Re: kdump regression compared to v2.6.35

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]

Message-ID: <4C7A42AA.1000806@kernel.org>
Date:	Sun, 29 Aug 2010 13:21:14 +0200
From:	Tejun Heo <tj@...nel.org>
To:	CAI Qian <caiqian@...hat.com>
CC:	kexec <kexec@...ts.infradead.org>, linux-next@...r.kernel.org,
	torvalds@...ux-foundation.org,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: kdump regression compared to v2.6.35

Hello,

On 08/29/2010 01:24 PM, CAI Qian wrote:
>> On 08/29/2010 09:01 AM, caiqian@...hat.com wrote:
>>> Further bisect indicated this bad commit from the merge. Given kdump
>>> kernel was running with maxcpus=1, I guess this work caused fs/bio.c
>>> hung in the workqueue on UP. Reverted the whole merge let kdump work
>>> again.
>>
>> Can you please pull from the following git tree and see whether it
>> fixes the problem?  There was a bug in nr_active accounting.
>
> It had the same problem.

I see.  Hmm... a different issue then.  Can you please tell me how to
reproduce the problem?

Thanks.

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