On 10 November 2014 17:56, Prarit Bhargava <[email protected]> wrote:
>> I still fail to understand why ? What will the _trylock() change ?
>
> viresh, afaict read_trylock will return 0 when busy with write:
Yes..
> static inline int queue_read_trylock(struct qrwlock *lock)
> {
> u32 cnts;
>
> cnts = atomic_read(&lock->cnts);
> if (likely(!(cnts & _QW_WMASK))) {
>
> so the deadlock will not occur. the show() is opened, write lock is taken,
> and
> if the thread is rescheduled and takes read lock the trylock will return 0,
> and
> the thread will return -EBUSY to userspace avoiding the deadlock.
Which deadlock? And also your changelog talks about accessing invalid pointers
without the trylock change, how can that be possible? After the read
lock is taken,
all the pointers should be valid.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
