linux-kernel - Re: [RFC V2 PATCH] kernfs: create raw version kernfs_path_len and kernfs

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 27 Feb 2016 06:41:37 -0500
From:	Tejun Heo <tj@...nel.org>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Yang Shi <yang.shi@...aro.org>, gregkh@...uxfoundation.org,
	lizefan@...wei.com, rostedt@...dmis.org, bigeasy@...utronix.de,
	linux-kernel@...r.kernel.org, linux-rt-users@...r.kernel.org,
	linaro-kernel@...ts.linaro.org
Subject: Re: [RFC V2 PATCH] kernfs: create raw version kernfs_path_len and
 kernfs_path

On Sat, Feb 27, 2016 at 12:37:23PM +0100, Thomas Gleixner wrote:
> On Sat, 27 Feb 2016, Tejun Heo wrote:
> > On Fri, Feb 26, 2016 at 01:47:39PM -0800, Yang Shi wrote:
> > > Call synchronize_sched() when kernfs_node is updated since tracepoints are
> > > protected by rcu_read_lock_sched.
> > 
> > Adding synchronize_sched() to operations which can be triggered from
> > userland usually turns out to be problematic.  If this can't be solved
> > any other way, I think the right thing to do is replacing the path
> > with cgroup id as Christoph suggested.
> 
> Agreed. The path is not that important, right?

It can be, but we can print out the ino and userland can match that up
with path if necessary.

Thanks.

-- 
tejun