[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190624205810.GD26422@redhat.com>
Date: Mon, 24 Jun 2019 16:58:10 -0400
From: "Frank Ch. Eigler" <fche@...hat.com>
To: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
Cc: Peter Zijlstra <peterz@...radead.org>,
Jessica Yu <jeyu@...nel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
Josh Poimboeuf <jpoimboe@...hat.com>, jikos@...nel.org,
mbenes@...e.cz, Petr Mladek <pmladek@...e.com>,
Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Andrew Morton <akpm@...ux-foundation.org>,
Robert Richter <rric@...nel.org>,
rostedt <rostedt@...dmis.org>, Ingo Molnar <mingo@...hat.com>,
Martin KaFai Lau <kafai@...com>,
Song Liu <songliubraving@...com>, Yonghong Song <yhs@...com>,
paulmck <paulmck@...ux.ibm.com>,
"Joel Fernandes, Google" <joel@...lfernandes.org>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>,
Thomas Gleixner <tglx@...utronix.de>,
oprofile-list@...ts.sf.net, netdev <netdev@...r.kernel.org>,
bpf@...r.kernel.org
Subject: Re: [PATCH 2/3] module: Fix up module_notifier return values.
Hi -
> > While auditing all module notifiers I noticed a whole bunch of fail
> > wrt the return value. Notifiers have a 'special' return semantics.
>From peterz's comments, the patches, it's not obvious to me how one is
to choose between 0 (NOTIFY_DONE) and 1 (NOTIFY_OK) in the case of a
routine success.
> [...]
> I have a similar erroneous module notifier return value pattern
> in lttng-modules as well. I'll go fix it right away. CCing
> Frank Eigler from SystemTAP which AFAIK use a copy of
> lttng-tracepoint.c in their project, which should be fixed
> as well. I'm pasting the lttng-modules fix below.
Sure, following suit. Thanks.
- FChE
Powered by blists - more mailing lists