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  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]
Date:   Thu, 6 Jun 2019 11:46:21 -0600
From:   Mathieu Poirier <mathieu.poirier@...aro.org>
To:     Suzuki K Poulose <suzuki.poulose@....com>
Cc:     linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v4 0/4] coresight: Do not call smp_processor_id from
 pre-emptible contexts

On Thu, 6 Jun 2019 at 10:17, Suzuki K Poulose <suzuki.poulose@....com> wrote:
>
> We have a few places where we call smp_processor_id() from preemptible
> contexts during the perf buffer handling. We do this to figure out the
> numa node for the allocation in case the event is not CPU bound. Instead
> use NUMA_NO_NODE to avoid a splat.
>
>
> Changes since v3:
>  - No function changes. Fix the commit description
> Changes since V2:
>  - Use NUMA_NO_NODE instead of numa_node_id() for event->cpu == -1. (Robin Murphy)
>
>
> Suzuki K Poulose (4):
>   coresight: tmc-etr: Do not call smp_processor_id() from preemptible
>   coresight: tmc-etr: alloc_perf_buf: Do not call smp_processor_id from
>     preemptible
>   coresight: tmc-etf: Do not call smp_processor_id from preemptible
>   coresight: etb10: Do not call smp_processor_id from preemptible
>
>  drivers/hwtracing/coresight/coresight-etb10.c   |  6 ++----
>  drivers/hwtracing/coresight/coresight-tmc-etf.c |  6 ++----
>  drivers/hwtracing/coresight/coresight-tmc-etr.c | 13 ++++---------
>  3 files changed, 8 insertions(+), 17 deletions(-)

And this set.

Thanks,
Mathieu

>
> --
> 2.7.4
>

Powered by blists - more mailing lists