linux-kernel - Re: [for-next][PATCH 14/14] tracing: Get trace_array ref counts when accessing trace files

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:	Sat, 5 Apr 2014 14:33:26 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Sasha Levin <sasha.levin@...cle.com>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Alexander Lam <azl@...gle.com>
Subject: Re: [for-next][PATCH 14/14] tracing: Get trace_array ref counts
 when accessing trace files

On Sat, 05 Apr 2014 10:59:10 -0400
Sasha Levin <sasha.levin@...cle.com> wrote:

> On 07/02/2013 04:22 PM, Steven Rostedt wrote:
> > From: "Steven Rostedt (Red Hat)" <rostedt@...dmis.org>
> > 
> > When a trace file is opened that may access a trace array, it must
> > increment its ref count to prevent it from being deleted.
> > 
> > Cc: stable@...r.kernel.org # 3.10
> > Reported-by: Alexander Lam <azl@...gle.com>
> > Signed-off-by: Steven Rostedt <rostedt@...dmis.org>
> 
> Hi Steven,
> 
> This patch seems to cause the following lockdep warning:
> 

Thanks for the update. I run all my tests with lockdep enabled. I'm
wondering if your config enable a lock that I don't have in my configs.
Could you send me your .config please.

Thanks!

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