linux-kernel - Re: Need to take dev->sem, do it directly or use wrapper?

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]

Date:	Mon, 4 Jan 2010 12:04:36 -0800
From:	Greg KH <gregkh@...e.de>
To:	Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Need to take dev->sem, do it directly or use wrapper?

On Mon, Jan 04, 2010 at 10:50:23AM -0800, Dmitry Torokhov wrote:
> Greg,
> 
> I was looking at restructuring serio a bit and rely more on the
> infrastructure in the drivre core now that it is more flexible. It all
> looks good except for one detail - serio provides "reconnect" method
> which allows user to reinitialize a port whithout tearing down its
> children input devices. To properly serialize with probe(), remove() and
> other bus operations I'd need to take dev->sem semaphore. I(s bus code
> allowed to do this? Can I do it directly or we need to add a wrapper
> (like device_serialize_access(dev, bool))?

Adding a wrapper would be best to do.

thanks,

greg k-h
--
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/