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  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:	Sat, 19 May 2007 10:29:04 +0200
From:	"Rafael J. Wysocki" <>
To:	"Robert P. J. Day" <>
Cc:	Linux Kernel Mailing List <>,
	Oleg Nesterov <>
Subject: Re: why only one use of "create_freezeable_workqueue"?

On Saturday, 19 May 2007 06:09, Robert P. J. Day wrote:
>   hoping to avoid the madness following my earlier, innocuous question
> about the lonely, defconfig'ed module scsi_wait_scan.ko, i'm curious
> about why there is, in the entire tree, just one invocation of
> "create_freezeable_workqueue":
> $ grep -rw create_freezeable_workqueue *
> drivers/misc/tifm_core.c:       workqueue = create_freezeable_workqueue("tifm");
> include/linux/workqueue.h:#define create_freezeable_workqueue(name) __create_workqueue((name), 1, 1)
> $
>   not that there's anything wrong with that, but i'm just curious as
> to why there's only one application of that feature in the whole tree.

Because the feature has limitted functionality (signlethread workqueues only),
needs some more work and the use of it is discouraged (for now).

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists