linux-kernel - Re: [PATCH 1/3] printk: Release console_sem after logbuf

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: <20110609170804.1b76e853.akpm@linux-foundation.org>
Date:	Thu, 9 Jun 2011 17:08:04 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Hugh Dickins <hughd@...gle.com>
Cc:	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Ingo Molnar <mingo@...e.hu>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel@...r.kernel.org, efault@....de,
	Arne Jansen <lists@...-jansens.de>
Subject: Re: [PATCH 1/3] printk: Release console_sem after logbuf_lock

On Thu, 9 Jun 2011 16:57:29 -0700 (PDT)
Hugh Dickins <hughd@...gle.com> wrote:

> Does your mail below stir any useful memories?

Thanks.  I did have the email, but it didn't match any of my grep
patterns.

> Some notes:

Stupid thing doesn't explain the magical locking though :( I'm 99.9%
sure that putting an up() inside a spinlock_irq()ed region was
deliberate.

> - Being heartily sick of reverse-engineering interface information
>   from implementations, I have gratuitously added comments in several
>   random parts of the kernel.  Shoot me.

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