linux-kernel - Re: [PATCH 1/4] workqueue: Create low-level unbound workqueues cpumask

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:	Thu, 1 May 2014 11:13:02 -0400
From:	Tejun Heo <tj@...nel.org>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Christoph Lameter <cl@...ux.com>,
	Kevin Hilman <khilman@...aro.org>,
	Lai Jiangshan <laijs@...fujitsu.com>,
	Mike Galbraith <bitbucket@...ine.de>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Viresh Kumar <viresh.kumar@...aro.org>
Subject: Re: [PATCH 1/4] workqueue: Create low-level unbound workqueues
 cpumask

On Thu, May 01, 2014 at 05:09:20PM +0200, Frederic Weisbecker wrote:
> > > Not sure why you want that. It makes sense on directories grouping
> > > file for different subsystem. But here?
> > 
> > Worried about possible conflicts with workqueue names if we end up
> > with more attributes.
> 
> But they are already protected in their own directories. Also having
> the same file attribute names in root and in individual directories
> suggests that root attributes primes on the childs.

Yeah but workqueues already tend to have pretty short and fundamental
names, and it can get confusing to have mix of files and directories
all with short names without much recognizable pattern.  I don't know.
Maybe I'm worrying too much but I'd really hate to be in a situation
where an attribute has to be renamed because it conflicts with a
workqueue name.

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