On Fri, Sep 02, 2016 at 11:05:09AM +0300, Pavel Andrianov wrote: > > Hi! > > There is a potential race in drivers/iio/adc/vf610_adc.ko. > Handlers vf610_set_conversion_mode and vf610_write_raw are called via > device_attibute interface, but they are related to different attributes, so > may be executed in parallel. vf610_set_conversion_mode acquires the mutex > indio_dev->mlock, and vf610_write_raw does not. Thus updating the structure > 'info' may be performed simultaneously. > > Should vf610_write_raw also acquire the same mutex indio_dev->mlock? > Hi Pavel, I'm not familiar with the conversion_mode interface, so I'll leave your specific question for someone with that knowledge. Just wanted to point out that if you're going to update the locking in the driver, there are 2 things to consider: 1) Use iio_device_claim_direct_mode() helper functions instead of checking iio_buffer_enabled and grabbing mlock. 2) Any other uses of indio_dev->mlock are best moved to a private data lock. We want to return that mlock to an INTERNAL (core) use only. alisons > -- > Pavel Andrianov > Linux Verification Center, ISPRAS > web: http://linuxtesting.org > e-mail: andrianov@xxxxxxxxx > -- > To unsubscribe from this list: send the line "unsubscribe linux-iio" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-iio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
