From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: "Ian Rogers" <irogers@google.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Ingo Molnar" <mingo@redhat.com>,
"Mark Rutland" <mark.rutland@arm.com>,
"Alexander Shishkin" <alexander.shishkin@linux.intel.com>,
"Jiri Olsa" <jolsa@kernel.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Darren Hart" <dvhart@infradead.org>,
"Davidlohr Bueso" <dave@stgolabs.net>,
"André Almeida" <andrealmeid@igalia.com>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nick Desaulniers" <ndesaulniers@google.com>,
"Tom Rix" <trix@redhat.com>, "Weiguo Li" <liwg06@foxmail.com>,
"Athira Rajeev" <atrajeev@linux.vnet.ibm.com>,
"Thomas Richter" <tmricht@linux.ibm.com>,
"Ravi Bangoria" <ravi.bangoria@amd.com>,
"Dario Petrillo" <dario.pk1@gmail.com>,
Hewenliang <hewenliang4@huawei.com>,
yaowenbin <yaowenbin1@huawei.com>,
"Wenyu Liu" <liuwenyu7@huawei.com>,
"Song Liu" <songliubraving@fb.com>,
"Andrii Nakryiko" <andrii@kernel.org>,
"Dave Marchevsky" <davemarchevsky@fb.com>,
"Leo Yan" <leo.yan@linaro.org>,
"Kim Phillips" <kim.phillips@amd.com>,
"Pavithra Gurushankar" <gpavithrasha@gmail.com>,
"Alexandre Truong" <alexandre.truong@arm.com>,
"Quentin Monnet" <quentin@isovalent.com>,
"William Cohen" <wcohen@redhat.com>,
"Andres Freund" <andres@anarazel.de>,
"Adrian Hunter" <adrian.hunter@intel.com>,
"Martin Liška" <mliska@suse.cz>,
"Colin Ian King" <colin.king@intel.com>,
"James Clark" <james.clark@arm.com>,
"Fangrui Song" <maskray@google.com>,
"Stephane Eranian" <eranian@google.com>,
"Kajol Jain" <kjain@linux.ibm.com>,
"Alexey Bayduraev" <alexey.v.bayduraev@linux.intel.com>,
"Riccardo Mancini" <rickyman7@gmail.com>,
"Andi Kleen" <ak@linux.intel.com>,
"Masami Hiramatsu" <mhiramat@kernel.org>,
"Zechuan Chen" <chenzechuan1@huawei.com>,
"Jason Wang" <wangborong@cdjrlc.com>,
"Christophe JAILLET" <christophe.jaillet@wanadoo.fr>,
"Remi Bernon" <rbernon@codeweavers.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-perf-users <linux-perf-users@vger.kernel.org>,
bpf <bpf@vger.kernel.org>,
llvm@lists.linux.dev
Subject: Re: [PATCH v4 00/18] Mutex wrapper, locking and memory leak fixes
Date: Fri, 26 Aug 2022 16:21:04 -0300 [thread overview]
Message-ID: <YwkdIBsQEKXG3/rE@kernel.org> (raw)
In-Reply-To: <CAM9d7cgQZsbwWSdRNQqUE+GsSgPVqFmKs9LJ5b6ta2-dax5T2Q@mail.gmail.com>
Em Fri, Aug 26, 2022 at 12:08:06PM -0700, Namhyung Kim escreveu:
> On Fri, Aug 26, 2022 at 9:42 AM Ian Rogers <irogers@google.com> wrote:
> >
> > When fixing a locking race and memory leak in:
> > https://lore.kernel.org/linux-perf-users/20211118193714.2293728-1-irogers@google.com/
> >
> > It was requested that debug mutex code be separated out into its own
> > files. This was, in part, done by Pavithra Gurushankar in:
> > https://lore.kernel.org/lkml/20220727111954.105118-1-gpavithrasha@gmail.com/
> >
> > These patches fix issues with the previous patches, add in the
> > original dso->nsinfo fix and then build on our mutex wrapper with
> > clang's -Wthread-safety analysis. The analysis found missing unlocks
> > in builtin-sched.c which are fixed and -Wthread-safety is enabled by
> > default when building with clang.
> >
> > v4. Adds a comment for the trylock result, fixes the new line (missed
> > in v3) and removes two blank lines as suggested by Adrian Hunter.
> > v3. Adds a missing new line to the error messages and removes the
> > pshared argument to mutex_init by having two functions, mutex_init
> > and mutex_init_pshared. These changes were suggested by Adrian Hunter.
> > v2. Breaks apart changes that s/pthread_mutex/mutex/g and the lock
> > annotations as requested by Arnaldo and Namhyung. A boolean is
> > added to builtin-sched.c to terminate thread funcs rather than
> > leaving them blocked on delted mutexes.
> >
> > Ian Rogers (17):
> > perf bench: Update use of pthread mutex/cond
> > perf tests: Avoid pthread.h inclusion
> > perf hist: Update use of pthread mutex
> > perf bpf: Remove unused pthread.h include
> > perf lock: Remove unused pthread.h include
> > perf record: Update use of pthread mutex
> > perf sched: Update use of pthread mutex
> > perf ui: Update use of pthread mutex
> > perf mmap: Remove unnecessary pthread.h include
> > perf dso: Update use of pthread mutex
> > perf annotate: Update use of pthread mutex
> > perf top: Update use of pthread mutex
> > perf dso: Hold lock when accessing nsinfo
> > perf mutex: Add thread safety annotations
> > perf sched: Fixes for thread safety analysis
> > perf top: Fixes for thread safety analysis
> > perf build: Enable -Wthread-safety with clang
> >
> > Pavithra Gurushankar (1):
> > perf mutex: Wrapped usage of mutex and cond
>
> For the patches 1-7 and 10-13
>
> Acked-by: Namhyung Kim <namhyung@kernel.org>
Thanks added it, will try to get what is done so far merged and then we
can go on addressing the other issues brought up in this thread.
- Arnaldo
next prev parent reply other threads:[~2022-08-26 19:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 16:42 [PATCH v4 00/18] Mutex wrapper, locking and memory leak fixes Ian Rogers
2022-08-26 16:42 ` [PATCH v4 01/18] perf mutex: Wrapped usage of mutex and cond Ian Rogers
2022-08-26 16:42 ` [PATCH v4 02/18] perf bench: Update use of pthread mutex/cond Ian Rogers
2022-08-26 16:42 ` [PATCH v4 03/18] perf tests: Avoid pthread.h inclusion Ian Rogers
2022-08-26 16:42 ` [PATCH v4 04/18] perf hist: Update use of pthread mutex Ian Rogers
2022-08-26 16:42 ` [PATCH v4 05/18] perf bpf: Remove unused pthread.h include Ian Rogers
2022-08-26 16:42 ` [PATCH v4 06/18] perf lock: " Ian Rogers
2022-08-26 16:42 ` [PATCH v4 07/18] perf record: Update use of pthread mutex Ian Rogers
2022-08-26 16:42 ` [PATCH v4 08/18] perf sched: " Ian Rogers
2022-08-26 16:42 ` [PATCH v4 09/18] perf ui: " Ian Rogers
2022-08-26 16:42 ` [PATCH v4 10/18] perf mmap: Remove unnecessary pthread.h include Ian Rogers
2022-08-26 16:42 ` [PATCH v4 11/18] perf dso: Update use of pthread mutex Ian Rogers
2022-08-26 16:42 ` [PATCH v4 12/18] perf annotate: " Ian Rogers
2022-08-26 16:42 ` [PATCH v4 13/18] perf top: " Ian Rogers
2022-08-26 16:42 ` [PATCH v4 14/18] perf dso: Hold lock when accessing nsinfo Ian Rogers
2022-08-26 16:42 ` [PATCH v4 15/18] perf mutex: Add thread safety annotations Ian Rogers
2022-08-26 16:42 ` [PATCH v4 16/18] perf sched: Fixes for thread safety analysis Ian Rogers
2022-08-26 16:42 ` [PATCH v4 17/18] perf top: " Ian Rogers
2022-08-26 16:42 ` [PATCH v4 18/18] perf build: Enable -Wthread-safety with clang Ian Rogers
2022-08-26 19:08 ` [PATCH v4 00/18] Mutex wrapper, locking and memory leak fixes Namhyung Kim
2022-08-26 19:21 ` Arnaldo Carvalho de Melo [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-26 16:40 Ian Rogers
2022-08-27 7:04 ` Adrian Hunter
2022-08-27 15:18 ` Arnaldo Carvalho de Melo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YwkdIBsQEKXG3/rE@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexandre.truong@arm.com \
--cc=alexey.v.bayduraev@linux.intel.com \
--cc=andrealmeid@igalia.com \
--cc=andres@anarazel.de \
--cc=andrii@kernel.org \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=bpf@vger.kernel.org \
--cc=chenzechuan1@huawei.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=colin.king@intel.com \
--cc=dario.pk1@gmail.com \
--cc=dave@stgolabs.net \
--cc=davemarchevsky@fb.com \
--cc=dvhart@infradead.org \
--cc=eranian@google.com \
--cc=gpavithrasha@gmail.com \
--cc=hewenliang4@huawei.com \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--cc=kim.phillips@amd.com \
--cc=kjain@linux.ibm.com \
--cc=leo.yan@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=liuwenyu7@huawei.com \
--cc=liwg06@foxmail.com \
--cc=llvm@lists.linux.dev \
--cc=mark.rutland@arm.com \
--cc=maskray@google.com \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=mliska@suse.cz \
--cc=namhyung@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=peterz@infradead.org \
--cc=quentin@isovalent.com \
--cc=ravi.bangoria@amd.com \
--cc=rbernon@codeweavers.com \
--cc=rickyman7@gmail.com \
--cc=songliubraving@fb.com \
--cc=tglx@linutronix.de \
--cc=tmricht@linux.ibm.com \
--cc=trix@redhat.com \
--cc=wangborong@cdjrlc.com \
--cc=wcohen@redhat.com \
--cc=yaowenbin1@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).