Daniel WagnerandGreg Kroah-Hartman a7d0b6c253 nvmet-fcloop: access fcpreq only when holding reqlock ...

[ Upstream commit 47a827cd79 ]

The abort handling logic expects that the state and the fcpreq are only
accessed when holding the reqlock lock.

While at it, only handle the aborts in the abort handler.

Signed-off-by: Daniel Wagner <wagi@kernel.org>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Sasha Levin <sashal@kernel.org>

2025-06-27 11:07:24 +01:00

..

admin-cmd.c

…

auth.c

…

configfs.c

…

core.c

…

discovery.c

…

fabrics-cmd-auth.c

…

fabrics-cmd.c

…

fc.c

nvmet-fc: put ref when assoc->del_work is already scheduled

2025-05-02 07:47:06 +02:00

fcloop.c

nvmet-fcloop: access fcpreq only when holding reqlock

2025-06-27 11:07:24 +01:00

io-cmd-bdev.c

nvmet: propagate npwg topology

2025-01-23 17:17:11 +01:00

io-cmd-file.c

…

Kconfig

…

loop.c

…

Makefile

…

nvmet.h

…

passthru.c

…

rdma.c

nvmet-rdma: recheck queue state is LIVE in state lock in recv done

2025-03-28 21:58:52 +01:00

tcp.c

nvmet-tcp: don't restore null sk_state_change

2025-06-04 14:40:18 +02:00

trace.c

…

trace.h

…

zns.c

…