[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20211108112313.73d0727e@gandalf.local.home>
Date: Mon, 8 Nov 2021 11:23:13 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Borislav Petkov <bp@...en8.de>
Cc: Alan Stern <stern@...land.harvard.edu>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
LKML <linux-kernel@...r.kernel.org>,
Arnd Bergmann <arnd@...db.de>,
Ayush Sawal <ayush.sawal@...lsio.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Rohit Maheshwari <rohitm@...lsio.com>,
Vinay Kumar Yadav <vinay.yadav@...lsio.com>,
alsa-devel@...a-project.org, bcm-kernel-feedback-list@...adcom.com,
intel-gfx@...ts.freedesktop.org,
intel-gvt-dev@...ts.freedesktop.org, linux-alpha@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-clk@...r.kernel.org,
linux-crypto@...r.kernel.org, linux-edac@...r.kernel.org,
linux-fbdev@...r.kernel.org, linux-hyperv@...r.kernel.org,
linux-iio@...r.kernel.org, linux-leds@...r.kernel.org,
linux-mips@...r.kernel.org, linux-parisc@...r.kernel.org,
linux-pm@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org,
linux-remoteproc@...r.kernel.org,
linux-renesas-soc@...r.kernel.org, linux-s390@...r.kernel.org,
linux-scsi@...r.kernel.org, linux-sh@...r.kernel.org,
linux-staging@...ts.linux.dev, linux-tegra@...r.kernel.org,
linux-um@...ts.infradead.org, linux-usb@...r.kernel.org,
linux-xtensa@...ux-xtensa.org, netdev@...r.kernel.org,
openipmi-developer@...ts.sourceforge.net, rcu@...r.kernel.org,
sparclinux@...r.kernel.org, x86@...nel.org,
xen-devel@...ts.xenproject.org
Subject: Re: [PATCH v0 00/42] notifiers: Return an error when callback is
already registered
On Mon, 8 Nov 2021 15:35:50 +0100
Borislav Petkov <bp@...en8.de> wrote:
> On Mon, Nov 08, 2021 at 03:24:39PM +0100, Borislav Petkov wrote:
> > I guess I can add another indirection to notifier_chain_register() and
> > avoid touching all the call sites.
>
> IOW, something like this below.
>
> This way I won't have to touch all the callsites and the registration
> routines would still return a proper value instead of returning 0
> unconditionally.
I prefer this method.
Question, how often does this warning trigger? Is it common to see in
development?
-- Steve
Powered by blists - more mailing lists