linux-kernel - Re: [PATCH 01/12] Use mutex instead of semaphore in driver core

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: <a8e1da0801021700s7aab56d4gc4c68aa6db5efce@mail.gmail.com>
Date:	Thu, 3 Jan 2008 09:00:58 +0800
From:	"Dave Young" <hidave.darkstar@...il.com>
To:	"Alan Stern" <stern@...land.harvard.edu>
Cc:	"Greg KH" <gregkh@...e.de>, "David Miller" <davem@...emloft.net>,
	"Greg KH" <greg@...ah.com>, peterz@...radead.org,
	"Kernel development list" <linux-kernel@...r.kernel.org>,
	"USB list" <linux-usb@...r.kernel.org>
Subject: Re: [PATCH 01/12] Use mutex instead of semaphore in driver core

On Jan 3, 2008 12:08 AM, Alan Stern <stern@...land.harvard.edu> wrote:
> On Tue, 1 Jan 2008, Greg KH wrote:
>
> > For most cases, yes, I agree with this, but due to the lockdep issues
> > that occur here, and the whole mess with the suspend path and locking
> > the device tree, that has been hashed out many times in the past, I am
> > interested in trying to see if there is any real reason why this is
> > absolutely necessary to convert.
> >
> > If no one has noticed any issues in this area, I think the complexity
> > that will be involved in any such conversion will strongly outweigh any
> > simplicity that might be expected.
> >
> > I'm very open to potential patches to do this, just don't ignore the
> > issues that others have run into in the past when attempting this.
>
> There are two separate things to consider here.  One is struct device
> and the other is struct class.
>
> We know that replacing semaphores with mutexes in struct device doesn't
> sit well with lockdep.  However the replacement may work perfectly
> smoothly for struct class.  It would be worthwhile for Dave Young to
> separate out just that part and try it.
>
Ok, let me try a new patch only for struct class.

Regards
dave
--
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/