[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1453282570.2521.130.camel@linux.intel.com>
Date: Wed, 20 Jan 2016 11:36:10 +0200
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: "Yankejian (Hackim Yim)" <yankejian@...wei.com>,
Yisen Zhuang <Yisen.zhuang@...wei.com>, davem@...emloft.net,
robh+dt@...nel.org, pawel.moll@....com, mark.rutland@....com,
ijc+devicetree@...lion.org.uk, galak@...eaurora.org,
catalin.marinas@....com, will.deacon@....com,
huangdaode@...ilicon.com, liguozhu@...wei.com, arnd@...db.de,
fengguang.wu@...el.com, salil.mehta@...wei.com,
lisheng011@...wei.com
Cc: devicetree@...r.kernel.org, netdev@...r.kernel.org,
linuxarm@...wei.com, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v2 next-next] net: hns: enet specifies a reference to
dsaf
On Wed, 2016-01-20 at 14:49 +0800, Yankejian (Hackim Yim) wrote:
> > > +
> > > > > > + snprintf(ae_dev->name, AE_NAME_SIZE, "%s%d",
> > > > > > DSAF_DEVICE_NAME,
> > > > > > + (int)atomic_inc_return(&id));
> > If you bind/unbind device enough times you may get an overflow and
> > end
> > up with name of existing device (if you have 1+ of them in the
> > system).
> >
> > To avoid such situation better to use IDA/IDR framework.
> >
> Hi, Andy
> Thanks again for your suggestion.
> It seems that using IDA/IDR framework is better, but all of the
> functions must be serialized by lock.
AFAIR it's designed in a way you don't need to do any additional
locking or synchronization.
--
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Intel Finland Oy
Powered by blists - more mailing lists