linux-kernel - Re: [PATCH] perf: extend total_ref_count usage to protect perf_trace

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:   Mon, 18 Mar 2019 16:15:29 +0100
From:   Peter Zijlstra <peterz@...radead.org>
To:     Steven Rostedt <rostedt@...dmis.org>
Cc:     Prateek Sood <prsood@...eaurora.org>, mingo@...hat.com,
        linux-kernel@...r.kernel.org, sramana@...eaurora.org,
        Frederic Weisbecker <fweisbec@...il.com>,
        Jiri Olsa <jolsa@...hat.com>
Subject: Re: [PATCH] perf: extend total_ref_count usage to protect
 perf_trace_buf access

On Mon, Mar 18, 2019 at 11:02:50AM -0400, Steven Rostedt wrote:
> On Mon, 18 Mar 2019 16:17:45 +0530
> Prateek Sood <prsood@...eaurora.org> wrote:
> 
> > A potential race exists between access of perf_trace_buf[i] from
> > perf_trace_buf_alloc() and perf_trace_event_unreg(). This can
> > result in perf_trace_buf[i] being NULL during access from memset()
> > in perf_trace_buf_alloc().

Can you expound?