linux-kernel - Re: [PATCH] debug_check_no_locks_freed: fix in

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]

Date:	Sat, 24 Nov 2007 15:25:11 +0300
From:	Oleg Nesterov <oleg@...sign.ru>
To:	Torsten Kaiser <just.for.lkml@...glemail.com>
Cc:	Ingo Molnar <mingo@...e.hu>, Alasdair G Kergon <agk@...hat.com>,
	Milan Broz <mbroz@...hat.com>,
	Johannes Berg <johannes@...solutions.net>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] debug_check_no_locks_freed: fix in_range() checks

On 11/24, Torsten Kaiser wrote:
>
> On Nov 24, 2007 11:53 AM, Oleg Nesterov <oleg@...sign.ru> wrote:
> > Torsten, could you ack/nack this patch?
> 
> From looking at the code I would ack it.

Great.

> I will reapply agk-dm-dm-crypt-move-bio-submission-to-thread.patch and
> this patch and boot several times, but as the message was not
> triggered on every boot, this can't prove anything.

Regardless of any other possible problems, I think you found a real bug
in debug_check_no_locks_freed() which should be fixed.

Oleg.

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