linux-kernel - Re: [PATCH] ds1620: Push BKL down

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: <20080708205536.2020e2a1@the-village.bc.nu>
Date:	Tue, 8 Jul 2008 20:55:36 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Russell King <rmk+lkml@....linux.org.uk>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ds1620: Push BKL down

On Tue, 8 Jul 2008 21:08:42 +0100
Russell King <rmk+lkml@....linux.org.uk> wrote:

> On Thu, May 22, 2008 at 09:35:29PM +0100, Alan Cox wrote:
> > Push down the BKL and correct the ioctl return for unknown ioctls.
> 
> In principle, no issues with the patch, and I'd ack it.  However, I've
> made some comments about whether the BKL is needed in all these places.
> Whether your intention is just to push the BKL down or to actually
> eliminate it will of course determine whether you want to delete those.

My intention is to keep pushing until it becomes another maintainers
problem to push further. I'll revamp this diff when I have a bit of time
to get back around to it and I'll push down/remove the lock further in
accordance with your comments.

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/