Re: [RFC PATCH v1 4/5] node_device_udev: Take lock if driver->privateData is modified

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Apr 11, 2024 at 05:50 PM +0200, Boris Fiuczynski <fiuczy@xxxxxxxxxxxxx> wrote:
> Reviewed-by: Boris Fiuczynski <fiuczy@xxxxxxxxxxxxx>
>
> On 4/3/24 16:03, Marc Hartmayer wrote:
>> Since @driver->privateData is modified take the lock.
>> 
>> Question: In theory we could take the udevEventData->mdevctlLock?
>
> Isn't that protecting the access to the mdevctlMonitor?
> On the first sight scheduleMdevctlUpdate does not directly make use of 
> mdevctlMonitor.
>

That’s the question… what is the scope of @mdevctlLock :)

-- 
Kind regards / Beste Grüße
   Marc Hartmayer

IBM Deutschland Research & Development GmbH
Vorsitzender des Aufsichtsrats: Wolfgang Wendt
Geschäftsführung: David Faller
Sitz der Gesellschaft: Böblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294
_______________________________________________
Devel mailing list -- devel@xxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxx




[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]

  Powered by Linux