[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170308101914.GB15198@kroah.com>
Date: Wed, 8 Mar 2017 11:19:14 +0100
From: "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
To: "Reshetova, Elena" <elena.reshetova@...el.com>
Cc: Shaohua Li <shli@...nel.org>,
"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
"linux-s390@...r.kernel.org" <linux-s390@...r.kernel.org>,
"open-iscsi@...glegroups.com" <open-iscsi@...glegroups.com>,
Kees Cook <keescook@...omium.org>,
"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
David Windsor <dwindsor@...il.com>,
"peterz@...radead.org" <peterz@...radead.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-raid@...r.kernel.org" <linux-raid@...r.kernel.org>,
"linux-bcache@...r.kernel.org" <linux-bcache@...r.kernel.org>,
"target-devel@...r.kernel.org" <target-devel@...r.kernel.org>,
"linux-serial@...r.kernel.org" <linux-serial@...r.kernel.org>,
"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
"fcoe-devel@...n-fcoe.org" <fcoe-devel@...n-fcoe.org>,
"xen-devel@...ts.xenproject.org" <xen-devel@...ts.xenproject.org>,
"linux1394-devel@...ts.sourceforge.net"
<linux1394-devel@...ts.sourceforge.net>,
Hans Liljestrand <ishkamiel@...il.com>,
"linux-media@...r.kernel.org" <linux-media@...r.kernel.org>
Subject: Re: [PATCH 08/29] drivers, md: convert mddev.active from atomic_t to
refcount_t
On Wed, Mar 08, 2017 at 09:42:09AM +0000, Reshetova, Elena wrote:
> > On Mon, Mar 06, 2017 at 04:20:55PM +0200, Elena Reshetova wrote:
> > > refcount_t type and corresponding API should be
> > > used instead of atomic_t when the variable is used as
> > > a reference counter. This allows to avoid accidental
> > > refcounter overflows that might lead to use-after-free
> > > situations.
> >
> > Looks good. Let me know how do you want to route the patch to upstream.
>
> Greg, you previously mentioned that driver's conversions can go via your tree. Does this still apply?
> Or should I be asking maintainers to merge these patches via their trees?
You should ask them to take them through their trees, if they have them.
I'll be glad to scoop up all of the remaining ones that get missed, or
for subsystems that do not have trees.
thanks,
greg k-h
Powered by blists - more mailing lists