diff options
| author | Andreas Gruenbacher <agruenba@redhat.com> | 2025-02-05 19:16:38 +0300 |
|---|---|---|
| committer | Andreas Gruenbacher <agruenba@redhat.com> | 2025-03-10 20:15:38 +0300 |
| commit | a431d49243a012738f132054b2303e0815663aac (patch) | |
| tree | 7ed818af45907856b16c79b22f7fae923dd22fba /scripts/lib/kdoc/kdoc_parser.py | |
| parent | d838605fea6eabae3746a276fd448f6719eb3926 (diff) | |
| download | linux-a431d49243a012738f132054b2303e0815663aac.tar.xz | |
gfs2: Fix request cancelation bug
In finish_xmote(), when a locking request is canceled, the corresponding
holder is moved to the tail of the holders list instead of being
dequeued immediately. When there is only a single holder, the canceled
locking request is then immediately repeated. This makes no sense; it
looks like another remnant of LM_FLAG_PRIORITY support.
Instead, dequeue canceled holders and proceed with the next holder in
finish_xmote(). We can then easily detect in gfs2_glock_dq() when a
holder has been canceled.
Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>
Diffstat (limited to 'scripts/lib/kdoc/kdoc_parser.py')
0 files changed, 0 insertions, 0 deletions