diff options
author | Jens Axboe <axboe@kernel.dk> | 2023-10-02 19:51:38 -0600 |
---|---|---|
committer | Jens Axboe <axboe@kernel.dk> | 2023-10-03 08:12:54 -0600 |
commit | 1658633c04653578429ff5dfc62fdc159203a8f2 (patch) | |
tree | caab58969a6d936ba39f46c0432752c25ed59c33 /tools/net/ynl/generated/devlink-user.c | |
parent | f8024f1f36a30a082b0457d5779c8847cea57f57 (diff) |
io_uring: ensure io_lockdep_assert_cq_locked() handles disabled rings
io_lockdep_assert_cq_locked() checks that locking is correctly done when
a CQE is posted. If the ring is setup in a disabled state with
IORING_SETUP_R_DISABLED, then ctx->submitter_task isn't assigned until
the ring is later enabled. We generally don't post CQEs in this state,
as no SQEs can be submitted. However it is possible to generate a CQE
if tagged resources are being updated. If this happens and PROVE_LOCKING
is enabled, then the locking check helper will dereference
ctx->submitter_task, which hasn't been set yet.
Fixup io_lockdep_assert_cq_locked() to handle this case correctly. While
at it, convert it to a static inline as well, so that generated line
offsets will actually reflect which condition failed, rather than just
the line offset for io_lockdep_assert_cq_locked() itself.
Reported-and-tested-by: syzbot+efc45d4e7ba6ab4ef1eb@syzkaller.appspotmail.com
Fixes: f26cc9593581 ("io_uring: lockdep annotate CQ locking")
Cc: stable@vger.kernel.org
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'tools/net/ynl/generated/devlink-user.c')
0 files changed, 0 insertions, 0 deletions