linux-kernel - Re: [PATCH] amiserial: Prepare for locking relaxation in caller.

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: <20080223102758.0d42ccb3@core>
Date:	Sat, 23 Feb 2008 10:27:58 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] amiserial: Prepare for locking relaxation in caller.

On Sat, 23 Feb 2008 00:05:25 -0800
Andrew Morton <akpm@...ux-foundation.org> wrote:

> On Wed, 20 Feb 2008 20:11:01 +0000 Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
> 
> > 
> > Just wrap this one in a lock_kernel. As I understand it there is no M68K
> > SMP anyway.
> > 
> 
> I assume that all the bkl/locking patches are prerequisites for
> tty-bkl-pushdown.patch, and that they don't depend upon
> tty-bkl-pushdown.patch?

They are all prequisites for some changes I've yet to send you and will
do once I'm sure I've not upset anything in the meantime. There should be
no interdependancies although I've obviously not tested every possible
combination

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