David Howells wrote:
> [Adding Paul McKenney as he's the expert.]
>
> Akira Yokosawa wrote:
>
>> David Howells wrote:
>>> Use clear_and_wake_up_bit() rather than something like:
>>>
>>> clear_bit_unlock(NETFS_RREQ_IN_PROGRESS, &rreq->flags);
>>> wake_up_bit(&rreq->flags, NETFS_RREQ_IN_PR
[Adding Paul McKenney as he's the expert.]
Akira Yokosawa wrote:
> David Howells wrote:
> > Use clear_and_wake_up_bit() rather than something like:
> >
> > clear_bit_unlock(NETFS_RREQ_IN_PROGRESS, &rreq->flags);
> > wake_up_bit(&rreq->flags, NETFS_RREQ_IN_PROGRESS);
> >
> > as there ne
Hi David,
David Howells wrote:
> Use clear_and_wake_up_bit() rather than something like:
>
> clear_bit_unlock(NETFS_RREQ_IN_PROGRESS, &rreq->flags);
> wake_up_bit(&rreq->flags, NETFS_RREQ_IN_PROGRESS);
>
> as there needs to be a barrier inserted between which is present in
> clear_an
Use clear_and_wake_up_bit() rather than something like:
clear_bit_unlock(NETFS_RREQ_IN_PROGRESS, &rreq->flags);
wake_up_bit(&rreq->flags, NETFS_RREQ_IN_PROGRESS);
as there needs to be a barrier inserted between which is present in
clear_and_wake_up_bit().
Fixes: 288ace2f57c9 ("ne