On Wed, May 09, 2018 at 03:32:16PM +0200, Geert Uytterhoeven wrote:
> Hi Russell,
>
> On Wed, May 9, 2018 at 12:39 PM, Russell King - ARM Linux
> wrote:
> > On Thu, Apr 26, 2018 at 10:45:49AM +0200, Geert Uytterhoeven wrote:
> >> On Thu, Apr 26, 2018 at 10:35 AM, Greg
On Wed, May 09, 2018 at 03:32:16PM +0200, Geert Uytterhoeven wrote:
> Hi Russell,
>
> On Wed, May 9, 2018 at 12:39 PM, Russell King - ARM Linux
> wrote:
> > On Thu, Apr 26, 2018 at 10:45:49AM +0200, Geert Uytterhoeven wrote:
> >> On Thu, Apr 26, 2018 at 10:35 AM, Greg Kroah-Hartman
> >> wrote:
Hi Russell,
On Wed, May 9, 2018 at 12:39 PM, Russell King - ARM Linux
wrote:
> On Thu, Apr 26, 2018 at 10:45:49AM +0200, Geert Uytterhoeven wrote:
>> On Thu, Apr 26, 2018 at 10:35 AM, Greg Kroah-Hartman
>> wrote:
>> > On Thu, Apr 26, 2018 at
Hi Russell,
On Wed, May 9, 2018 at 12:39 PM, Russell King - ARM Linux
wrote:
> On Thu, Apr 26, 2018 at 10:45:49AM +0200, Geert Uytterhoeven wrote:
>> On Thu, Apr 26, 2018 at 10:35 AM, Greg Kroah-Hartman
>> wrote:
>> > On Thu, Apr 26, 2018 at 09:40:08AM +0200, Geert Uytterhoeven wrote:
>> >> On
On Thu, Apr 26, 2018 at 10:45:49AM +0200, Geert Uytterhoeven wrote:
> Hi Greg,
>
> On Thu, Apr 26, 2018 at 10:35 AM, Greg Kroah-Hartman
> wrote:
> > On Thu, Apr 26, 2018 at 09:40:08AM +0200, Geert Uytterhoeven wrote:
> >> On Thu, Apr 26, 2018 at 9:04 AM, Greg
On Thu, Apr 26, 2018 at 10:45:49AM +0200, Geert Uytterhoeven wrote:
> Hi Greg,
>
> On Thu, Apr 26, 2018 at 10:35 AM, Greg Kroah-Hartman
> wrote:
> > On Thu, Apr 26, 2018 at 09:40:08AM +0200, Geert Uytterhoeven wrote:
> >> On Thu, Apr 26, 2018 at 9:04 AM, Greg Kroah-Hartman
> >> wrote:
> >> > On
Hi Greg,
On Thu, Apr 26, 2018 at 10:35 AM, Greg Kroah-Hartman
wrote:
> On Thu, Apr 26, 2018 at 09:40:08AM +0200, Geert Uytterhoeven wrote:
>> On Thu, Apr 26, 2018 at 9:04 AM, Greg Kroah-Hartman
>> wrote:
>> > On Wed, Apr 25, 2018 at
Hi Greg,
On Thu, Apr 26, 2018 at 10:35 AM, Greg Kroah-Hartman
wrote:
> On Thu, Apr 26, 2018 at 09:40:08AM +0200, Geert Uytterhoeven wrote:
>> On Thu, Apr 26, 2018 at 9:04 AM, Greg Kroah-Hartman
>> wrote:
>> > On Wed, Apr 25, 2018 at 07:53:06PM +0200, Geert Uytterhoeven wrote:
>> >> On Wed, Apr
On Thu, Apr 26, 2018 at 09:40:08AM +0200, Geert Uytterhoeven wrote:
> Hi Greg,
>
> On Thu, Apr 26, 2018 at 9:04 AM, Greg Kroah-Hartman
> wrote:
> > On Wed, Apr 25, 2018 at 07:53:06PM +0200, Geert Uytterhoeven wrote:
> >> On Wed, Apr 25, 2018 at 6:06 PM, Greg
On Thu, Apr 26, 2018 at 09:40:08AM +0200, Geert Uytterhoeven wrote:
> Hi Greg,
>
> On Thu, Apr 26, 2018 at 9:04 AM, Greg Kroah-Hartman
> wrote:
> > On Wed, Apr 25, 2018 at 07:53:06PM +0200, Geert Uytterhoeven wrote:
> >> On Wed, Apr 25, 2018 at 6:06 PM, Greg Kroah-Hartman
> >> wrote:
> >> > On
Hi Greg,
On Thu, Apr 26, 2018 at 9:04 AM, Greg Kroah-Hartman
wrote:
> On Wed, Apr 25, 2018 at 07:53:06PM +0200, Geert Uytterhoeven wrote:
>> On Wed, Apr 25, 2018 at 6:06 PM, Greg Kroah-Hartman
>> wrote:
>> > On Tue, Apr 10, 2018 at
Hi Greg,
On Thu, Apr 26, 2018 at 9:04 AM, Greg Kroah-Hartman
wrote:
> On Wed, Apr 25, 2018 at 07:53:06PM +0200, Geert Uytterhoeven wrote:
>> On Wed, Apr 25, 2018 at 6:06 PM, Greg Kroah-Hartman
>> wrote:
>> > On Tue, Apr 10, 2018 at 03:21:44PM +0200, Geert Uytterhoeven wrote:
>> >> The
On Wed, Apr 25, 2018 at 07:53:06PM +0200, Geert Uytterhoeven wrote:
> Hi Greg,
>
> On Wed, Apr 25, 2018 at 6:06 PM, Greg Kroah-Hartman
> wrote:
> > On Tue, Apr 10, 2018 at 03:21:44PM +0200, Geert Uytterhoeven wrote:
> >> The driver_override implementation is
On Wed, Apr 25, 2018 at 07:53:06PM +0200, Geert Uytterhoeven wrote:
> Hi Greg,
>
> On Wed, Apr 25, 2018 at 6:06 PM, Greg Kroah-Hartman
> wrote:
> > On Tue, Apr 10, 2018 at 03:21:44PM +0200, Geert Uytterhoeven wrote:
> >> The driver_override implementation is susceptible to a race condition
> >>
Hi Greg,
On Wed, Apr 25, 2018 at 6:06 PM, Greg Kroah-Hartman
wrote:
> On Tue, Apr 10, 2018 at 03:21:44PM +0200, Geert Uytterhoeven wrote:
>> The driver_override implementation is susceptible to a race condition
>> when different threads are reading vs storing a
Hi Greg,
On Wed, Apr 25, 2018 at 6:06 PM, Greg Kroah-Hartman
wrote:
> On Tue, Apr 10, 2018 at 03:21:44PM +0200, Geert Uytterhoeven wrote:
>> The driver_override implementation is susceptible to a race condition
>> when different threads are reading vs storing a different driver
>> override. Add
On Tue, Apr 10, 2018 at 03:21:44PM +0200, Geert Uytterhoeven wrote:
> The driver_override implementation is susceptible to a race condition
> when different threads are reading vs storing a different driver
> override. Add locking to avoid this race condition.
>
> Cfr. commits 6265539776a0810b
On Tue, Apr 10, 2018 at 03:21:44PM +0200, Geert Uytterhoeven wrote:
> The driver_override implementation is susceptible to a race condition
> when different threads are reading vs storing a different driver
> override. Add locking to avoid this race condition.
>
> Cfr. commits 6265539776a0810b
Reviewed-by: Todd Kjos
On Tue, Apr 10, 2018 at 6:21 AM, Geert Uytterhoeven
wrote:
> The driver_override implementation is susceptible to a race condition
> when different threads are reading vs storing a different driver
> override. Add locking to
Reviewed-by: Todd Kjos
On Tue, Apr 10, 2018 at 6:21 AM, Geert Uytterhoeven
wrote:
> The driver_override implementation is susceptible to a race condition
> when different threads are reading vs storing a different driver
> override. Add locking to avoid this race condition.
>
> Cfr. commits
The driver_override implementation is susceptible to a race condition
when different threads are reading vs storing a different driver
override. Add locking to avoid this race condition.
Cfr. commits 6265539776a0810b ("driver core: platform: fix race
condition with driver_override") and
The driver_override implementation is susceptible to a race condition
when different threads are reading vs storing a different driver
override. Add locking to avoid this race condition.
Cfr. commits 6265539776a0810b ("driver core: platform: fix race
condition with driver_override") and
22 matches
Mail list logo