* Regarding bug in phantom.c
@ 2020-07-21 21:30 Madhuparna Bhowmik
0 siblings, 0 replies; only message in thread
From: Madhuparna Bhowmik @ 2020-07-21 21:30 UTC (permalink / raw)
To: jirislaby, arnd; +Cc: andrianov, Linux Kernel Mailing List
Hi,
This is regarding a race-condition related bug found in phantom.c by
the Linux Driver Verification Project.
dev->status is accessed in phantom_release with dev->open_lock and in
phantom_isr() using dev->regs_lock therefore there can be a race
between updating dev->status in phantom_release() and phantom_status()
and reading it's value in phantom_isr().
I don't think there is any particular lock protecting dev->status
(like open_lock and regs_lock are for dev->opened and dev->oregs) and
also not sure why exactly dev->status is updated in phantom_status()
and just after that updated again in phantom_release().
It will be great if you could look into this bug.
Thank you,
Madhuparna
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2020-07-21 21:31 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-07-21 21:30 Regarding bug in phantom.c Madhuparna Bhowmik
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).