linux-kernel - Re: [PATCH] tracing: zero the pipe cpumask on alloc to avoid spurious -EBUSY

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: <20230831163331.6c90c963@rorschach.local.home>
Date:   Thu, 31 Aug 2023 16:33:31 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Zheng Yejian <zhengyejian1@...wei.com>
Cc:     Brian Foster <bfoster@...hat.com>,
        <linux-trace-kernel@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] tracing: zero the pipe cpumask on alloc to avoid
 spurious -EBUSY

On Thu, 31 Aug 2023 21:51:18 +0800
Zheng Yejian <zhengyejian1@...wei.com> wrote:

> > Hi,
> > 
> > I ran into this problem just recently on one of my test VMs immediately
> > after updating to a v6.5 base. A revert of the aforementioned commit
> > addressed the problem. I'm not terribly familiar with the tracing code,
> > but on further inspection I noticed the cpumask doesn't appear to be
> > initialized anywhere. I suppose this could alternatively do a
> > cpumask_clear() or whatever after allocation, but either way this
> > addresses the problem for me.  
> 
> Yes, pipe_cpumask must be initialized.

Can I add a Reviewed-by tag from you?

> 
> > 
> > Please CC on replies as I'm not subscribed to the list. Thanks.

That's the default with Linux kernel lists.

-- Steve