On Thu, Aug 22, 2019 at 8:55 PM Darrick J. Wong <darrick.wong@xxxxxxxxxx> wrote:
>
> ...which is clearly caused by xfs_setattr_nonsize failing to unlock the
> ILOCK after the xfs_qm_vop_chown_reserve call fails. Add the missing
> unlock.
Thanks for the quick fix.
I assume there's no real embargo on this, and we can just add it asap
to the xfs tree and mark it for stable, rather than do anything
outside the usual development path?
The security list rules do allow for a 5-working-day delay, but this
being "just" a local DoS thing I expect nobody really will argue for
it.
Anybody?
Linus
