linux-kernel - Re: [PATCH -v2] acpi: Fix possible recursive locking in hwregs.c

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: <CADZ9YHg7yKMkqwz3wjg+=jF_DBojAvUwADkXUBRXc=s0SsC1pA@mail.gmail.com>
Date:	Mon, 7 Nov 2011 18:13:58 +0600
From:	Rakib Mullick <rakib.mullick@...il.com>
To:	"Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	linux-acpi <linux-acpi@...r.kernel.org>,
	akpm@...ux-foundation.org, ming Lin <ming.m.lin@...el.com>,
	len.brown@...el.com
Subject: Re: [PATCH -v2] acpi: Fix possible recursive locking in hwregs.c

On Mon, Nov 7, 2011 at 1:46 AM, Srivatsa S. Bhat
<srivatsa.bhat@...ux.vnet.ibm.com> wrote:
> On 11/06/2011 08:48 PM, Rakib Mullick wrote:
>
> It would be a good idea to also give the lockdep warning in the changelog
> (though you triggered it in a modified kernel), since that would make
> it very clear as to what problem your patch is trying to solve.

At the time of this reply, it's been taken. So, I'll keep it on mind
for next time.

> [And please line-wrap your changelog to 80 characters at most, per line].
>
Gmail's email editor automatically puts break on a line, that's why I
didn't put any line break on changelog. While I was reading my patch
on lkml.org, I've noticed that it creates a big one line changelog,
which is a bit weird. So, will keep it under 80 line from next time.

> Code-wise, the patch looks good to me. So,
> Reviewed-by: Srivatsa S. Bhat <srivatsa.bhat@...ux.vnet.ibm.com>
>

Thanks,
Rakib
--
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/