[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190710055628.GB5778@kroah.com>
Date: Wed, 10 Jul 2019 07:56:28 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Xiaoming Ni <nixiaoming@...wei.com>
Cc: adobriyan@...il.com, akpm@...ux-foundation.org,
anna.schumaker@...app.com, arjan@...ux.intel.com,
bfields@...ldses.org, chuck.lever@...cle.com, davem@...emloft.net,
jlayton@...nel.org, luto@...nel.org, mingo@...nel.org,
Nadia.Derbey@...l.net, paulmck@...ux.vnet.ibm.com,
semen.protsenko@...aro.org, stable@...nel.org,
stern@...land.harvard.edu, tglx@...utronix.de,
torvalds@...ux-foundation.org, trond.myklebust@...merspace.com,
viresh.kumar@...aro.org, vvs@...tuozzo.com,
alex.huangjianhui@...wei.com, dylix.dailei@...wei.com,
linux-kernel@...r.kernel.org, linux-nfs@...r.kernel.org,
netdev@...r.kernel.org
Subject: Re: [PATCH v3 0/3] kernel/notifier.c: avoid duplicate registration
On Wed, Jul 10, 2019 at 11:09:07AM +0800, Xiaoming Ni wrote:
> Registering the same notifier to a hook repeatedly can cause the hook
> list to form a ring or lose other members of the list.
Then don't do that :)
Is there any in-kernel users that do do this? If so, please just fix
them.
thanks,
greg k-h
Powered by blists - more mailing lists