linux-kernel - Re: lockdep trace from prepare_bprm

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: <20130307183213.GA18022@redhat.com>
Date:	Thu, 7 Mar 2013 19:32:14 +0100
From:	Oleg Nesterov <oleg@...hat.com>
To:	Tejun Heo <tj@...nel.org>
Cc:	Dave Jones <davej@...hat.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Alexander Viro <viro@...iv.linux.org.uk>,
	Li Zefan <lizefan@...wei.com>, cgroups@...r.kernel.org
Subject: Re: lockdep trace from prepare_bprm_creds

On 03/07, Tejun Heo wrote:
>
> On Thu, Mar 07, 2013 at 10:01:39AM -0800, Tejun Heo wrote:
> >
> > Another possibility is moving cgroup_lock outside threadgroup_lock(),
> > which was impossible before because of cgroup_lock abuses in specific
> > controller implementations but most of that have been updated and we
> > should now be pretty close to being able to make cgroup_lock outer to
> > most other locks.  Appending a completely untested patch below.
>
> This probably doesn't help as the dependency involves i_mutex.

Confused... why?

Oleg.

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