[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170816102249.0c0d8d12@gandalf.local.home>
Date: Wed, 16 Aug 2017 10:22:49 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Borislav Petkov <bp@...en8.de>
Cc: "Luck, Tony" <tony.luck@...el.com>,
"Kani, Toshimitsu" <toshi.kani@....com>,
"rjw@...ysocki.net" <rjw@...ysocki.net>,
"lenb@...nel.org" <lenb@...nel.org>,
"mchehab@...nel.org" <mchehab@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
"linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>
Subject: Re: [PATCH v2 4/7] ghes_edac: avoid multiple calls to dmi_walk()
On Wed, 16 Aug 2017 16:03:50 +0200
Borislav Petkov <bp@...en8.de> wrote:
> > What's the likelihood of two calls to ghes_edac_register being done
> > simultaneously? Because two calls at the same time will get past this.
>
> Well, that thing gets called per GHES platform device and last time I
> checked they do get probed back-to-back but I'll check that again.
Maybe keep that original mutex just in case.
-- Steve
Powered by blists - more mailing lists