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:	Tue, 12 May 2015 12:59:26 +0530
From:	Shreyas B Prabhu <shreyas@...ux.vnet.ibm.com>
To:	rostedt@...dmis.org
CC:	linux-kernel@...r.kernel.org, mingo@...hat.com,
	aneesh.kumar@...ux.vnet.ibm.com, paulmck@...ux.vnet.ibm.com,
	preeti@...ux.vnet.ibm.com, mgorman@...e.de, namhyung@...nel.org,
	lizf@...fujitsu.com, acme@...hat.com
Subject: Re: [PATCH RESEND 0/3] tracing/mm: Fix suspicious rcu_dereference_check()
 usage warnings

Hi Steven,
On closer look, there is no particular maintainer who picks changes to
this file. Can you please pick these up?

On Friday 08 May 2015 10:50 PM, Shreyas B. Prabhu wrote:
> Since tracepoints use RCU for protection, they must not be called on
> offline cpus. Running with LOCKDEP enabled discovered few scenarios
> where trace points were called on offline cpus. These patches fix
> this by converting these trace events into conditonal trace events
> where condition is cpu_online(smp_processor_id())
> 
> Previous posting of the patchset can be found here:
> https://lkml.org/lkml/2015/4/28/512
> 
> This resend CCs people who added/edited the trace events in question.
> 
> Shreyas B. Prabhu (3):
>   tracing/mm: Don't trace kmem_cache_free on offline cpus
>   tracing/mm: Don't trace mm_page_free on offline cpus
>   tracing/mm: Don't trace mm_page_pcpu_drain on offline cpus
> 
>  include/trace/events/kmem.h | 26 ++++++++++++++++++++++----
>  1 file changed, 22 insertions(+), 4 deletions(-)
> 

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ