From: Steven Rostedt <rostedt@goodmis.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
mhiramat@kernel.org, bristot@redhat.com, jbaron@akamai.com,
torvalds@linux-foundation.org, tglx@linutronix.de,
mingo@kernel.org, namit@vmware.com, hpa@zytor.com,
luto@kernel.org, ard.biesheuvel@linaro.org, jpoimboe@redhat.com,
pbonzini@redhat.com, mathieu.desnoyers@efficios.com,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: [PATCH v4 01/18] notifier: Fix broken error handling pattern
Date: Fri, 1 May 2020 19:35:02 -0400 [thread overview]
Message-ID: <20200501193502.7c9b2b10@oasis.local.home> (raw)
In-Reply-To: <20200501202943.837409514@infradead.org>
On Fri, 01 May 2020 22:28:50 +0200
Peter Zijlstra <peterz@infradead.org> wrote:
> The current notifiers have the following error handling pattern all
> over the place:
>
> int err, nr;
>
> err = __foo_notifier_call_chain(&chain, val_up, v, -1, &nr);
> if (err & NOTIFIER_STOP_MASK)
> __foo_notifier_call_chain(&chain, val_down, v, nr-1, NULL)
>
> And aside from the endless repetition thereof, it is broken. Consider
> blocking notifiers; both calls take and drop the rwsem, this means
> that the notifier list can change in between the two calls, making @nr
> meaningless.
>
> Fix this by replacing all the __foo_notifier_call_chain() functions
> with foo_notifier_call_chain_robust() that embeds the above pattern,
> but ensures it is inside a single lock region.
>
> Note: I switched atomic_notifier_call_chain_robust() to use
> the spinlock, since RCU cannot provide the guarantee
> required for the recovery.
>
> Note: software_resume() error handling was broken afaict.
>
> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> Acked-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> ---
> include/linux/notifier.h | 15 +--
> kernel/cpu_pm.c | 48 ++++--------
> kernel/notifier.c | 144 ++++++++++++++++++++++---------------
> kernel/power/hibernate.c | 26 +++---
> kernel/power/main.c | 8 +-
> kernel/power/power.h | 3
> kernel/power/suspend.c | 14 +--
> kernel/power/user.c | 14 +--
> tools/power/pm-graph/sleepgraph.py | 2
> 9 files changed, 141 insertions(+), 133 deletions(-)
>
This looks like something that can go in outside this series.
-- Steve
next prev parent reply other threads:[~2020-05-01 23:35 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 20:28 [PATCH v4 00/18] Add static_call() Peter Zijlstra
2020-05-01 20:28 ` [PATCH v4 01/18] notifier: Fix broken error handling pattern Peter Zijlstra
2020-05-01 23:35 ` Steven Rostedt [this message]
2020-05-01 20:28 ` [PATCH v4 02/18] module: Fix up module_notifier return values Peter Zijlstra
2020-05-01 20:28 ` [PATCH v4 03/18] module: Properly propagate MODULE_STATE_COMING failure Peter Zijlstra
2020-05-01 20:28 ` [PATCH v4 04/18] jump_label,module: Fix module lifetime for __jump_label_mod_text_reserved Peter Zijlstra
2020-05-01 20:28 ` [PATCH v4 05/18] compiler.h: Make __ADDRESSABLE() symbol truly unique Peter Zijlstra
2020-05-01 20:28 ` [PATCH v4 06/18] static_call: Add basic static call infrastructure Peter Zijlstra
2020-05-05 21:21 ` Josh Poimboeuf
2020-05-01 20:28 ` [PATCH v4 07/18] static_call: Add inline " Peter Zijlstra
2020-05-05 22:10 ` Josh Poimboeuf
2020-05-06 16:15 ` Peter Zijlstra
2020-05-01 20:28 ` [PATCH v4 08/18] static_call: Avoid kprobes on inline static_call()s Peter Zijlstra
2020-05-01 20:28 ` [PATCH v4 09/18] x86/static_call: Add out-of-line static call implementation Peter Zijlstra
2020-05-06 16:16 ` Peter Zijlstra
2020-05-01 20:28 ` [PATCH v4 10/18] x86/static_call: Add inline static call implementation for x86-64 Peter Zijlstra
2020-05-01 20:29 ` [PATCH v4 11/18] static_call: Simple self-test Peter Zijlstra
2020-05-01 20:29 ` [PATCH v4 12/18] tracepoint: Optimize using static_call() Peter Zijlstra
2020-05-13 8:48 ` [tracepoint] 01edfaf177: WARNING:at_kernel/static_call.c:#__static_call_update kernel test robot
2020-05-15 17:13 ` Peter Zijlstra
2020-05-01 20:29 ` [PATCH v4 13/18] x86/alternatives: Teach text_poke_bp() to emulate RET Peter Zijlstra
2020-05-01 20:29 ` [PATCH v4 14/18] static_call: Add static_cond_call() Peter Zijlstra
2020-05-02 13:08 ` Rasmus Villemoes
2020-05-03 12:58 ` Peter Zijlstra
2020-05-04 7:20 ` Rasmus Villemoes
2020-05-04 20:14 ` Peter Zijlstra
2020-05-05 7:50 ` Rasmus Villemoes
2020-05-05 9:38 ` Peter Zijlstra
2020-05-05 9:36 ` Peter Zijlstra
2020-05-05 18:13 ` Nick Desaulniers
2020-05-05 18:27 ` Nick Desaulniers
2020-05-05 18:48 ` Linus Torvalds
2020-05-05 19:00 ` Mathieu Desnoyers
2020-05-05 19:57 ` Nick Desaulniers
2020-05-05 20:27 ` Mathieu Desnoyers
2020-05-06 13:55 ` Peter Zijlstra
2020-05-06 14:01 ` Mathieu Desnoyers
2020-05-06 16:18 ` Peter Zijlstra
2020-05-06 13:51 ` Peter Zijlstra
2020-05-06 16:00 ` Peter Zijlstra
2020-05-06 17:16 ` Linus Torvalds
2020-05-06 19:57 ` Andy Lutomirski
2020-05-06 17:24 ` Josh Poimboeuf
2020-05-06 17:58 ` Peter Zijlstra
2020-05-06 18:09 ` Josh Poimboeuf
2020-05-06 18:16 ` Peter Zijlstra
2020-05-08 15:27 ` Peter Zijlstra
2020-05-08 15:47 ` Josh Poimboeuf
2020-05-08 16:17 ` Peter Zijlstra
2020-05-01 20:29 ` [PATCH v4 15/18] static_call: Handle tail-calls Peter Zijlstra
2020-05-06 18:10 ` Peter Zijlstra
2020-05-01 20:29 ` [PATCH v4 16/18] static_call: Allow early init Peter Zijlstra
2020-05-06 21:15 ` Josh Poimboeuf
2020-05-08 13:31 ` Peter Zijlstra
2020-05-08 14:27 ` Josh Poimboeuf
2020-05-08 15:30 ` Peter Zijlstra
2020-05-01 20:29 ` [PATCH v4 17/18] x86/perf, static_call: Optimize x86_pmu methods Peter Zijlstra
2020-05-01 20:29 ` [PATCH v4 18/18] objtool: Clean up elf_write() condition Peter Zijlstra
2020-05-06 17:32 ` [PATCH v4 00/18] Add static_call() Josh Poimboeuf
2020-05-06 18:05 ` Peter Zijlstra
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=20200501193502.7c9b2b10@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=ard.biesheuvel@linaro.org \
--cc=bristot@redhat.com \
--cc=hpa@zytor.com \
--cc=jbaron@akamai.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=namit@vmware.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
/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