linux-kernel - Re: [PATCH] USB: sisusbvga: Remove the BKL from open

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: <w2t63a49ef41004260630o31d81ff0qd98cfdace7e73ce0@mail.gmail.com>
Date:	Mon, 26 Apr 2010 15:30:34 +0200
From:	Alessio Igor Bogani <abogani@...ware.it>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	Oliver Neukum <oneukum@...e.de>,
	Greg Kroah-Hartman <gregkh@...e.de>,
	Thomas Winischhofer <thomas@...ischhofer.net>,
	Mauro Carvalho Chehab <mchehab@...hat.com>,
	Pete Zaitcev <zaitcev@...hat.com>, linux-usb@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	"Fr??d??ric Weisbecker" <fweisbec@...il.com>
Subject: Re: [PATCH] USB: sisusbvga: Remove the BKL from open

Dear Mr. Bergmann,

2010/4/26 Arnd Bergmann <arnd@...db.de>:
>> >> BKL is not needed here because necessary locking is already provided
>> >> by mutex sisusb->lock.
[...]
> What about the BKL in the sisusb_ioctl()? It seems to follow the
> same logic, so I would think that you can simply remove the BKL
> from the module entirely, rather than only half of it.

It is what effectively I'm trying to do!

The first part of this work is already present in USB subsystem
maintainer tree (aka greg) at:
http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/patches/usb/usb-sisusbvga-remove-the-bkl-from-ioctl.patch

Ciao,
Alessio
--
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/