linux-kernel - Re: BUG: lock held when returning to user space

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]

Date:	Thu, 13 Mar 2008 18:39:06 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Daniel Walker <dwalker@...sta.com>
Cc:	Jiri Kosina <jkosina@...e.cz>,
	Frank Munzert <frankm@...ux.vnet.ibm.com>, mingo@...e.hu,
	linux-kernel@...r.kernel.org
Subject: Re: BUG: lock held when returning to user space

On Thu, 2008-03-13 at 08:43 -0700, Daniel Walker wrote:
> On Wed, 2008-03-12 at 22:40 +0100, Jiri Kosina wrote:
> 
> > No, as it is a real bug if you use mutexes in this way. What happens if 
> > process that has called open() on your device (and has not closed it yet) 
> > calls fork()? 
> > Another breakage scenario -- what if the filedescriptor is sent through 
> > unix socket to another process? etc.
> 
> There's a number of places where a semaphore is used across system
> calls. 
> 
> for instance the usb skeleton, 
> 	drivers/usb/usb-skeleton.c
> 
> Several of the watchdog drivers,
> 	drivers/watchdog/s3c2410_wdt.c
> 
> These need to be removed, but the usage is clearly not compatible with
> the mutex API ..
> 
> If you convert them to atomic counts then you loose the sleeping aspect
> of the semaphore, which you'd have to add back somehow.
> 
> The only API that seems straight forward is using complete's .. Then you
> get an atomic count and all the sleeping function calls you might want..
> (include/linux/completion.h) The problem with complete's is that you
> can't start them out at "1" or "completed" unless you actually run
> complete() once during initialization (that's kind of ugly) ..

A simple waitqueue would work.

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