linux-kernel - Re: [PATCH] perf/core: make sure group events are for the same cpu

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] [day] [month] [year] [list]

Message-ID: <594A185E.4060709@huawei.com>
Date:   Wed, 21 Jun 2017 14:55:26 +0800
From:   zhouchengming <zhouchengming1@...wei.com>
To:     Alexander Shishkin <alexander.shishkin@...ux.intel.com>
CC:     <mingo@...hat.com>, <peterz@...radead.org>,
        <linux-kernel@...r.kernel.org>, <acme@...nel.org>,
        <guohanjun@...wei.com>
Subject: Re: [PATCH] perf/core: make sure group events are for the same cpu

On 2017/6/20 21:08, Alexander Shishkin wrote:
> Zhou Chengming<zhouchengming1@...wei.com>  writes:
>
>> The else branch are broken for taskctx:
> This is not a good way to open a commit message.
>
>> two events can on the same taskctx, but on different cpu.
> How?

fd1 = perf_open_event(attr, pid, 0, -1, flags);
fd2 = perf_open_event(attr, pid, 1, fd1, flags);

fd1 will be the leader event,  fd2 will be the sibling event in the group.

And they are for the same task, so they will be put on the same taskctx successfully
if !move_group.

Obviously it's wrong, we can't concurrently schedule them as a group, since they are
on different cpu.

Thanks.

>
> Regards,
> --
> Alex
>
> .
>