nvme fix for Linux 6.12
Keith Busch
maintainerSame fix as the last week's nvme fix, but for nvme-multipath. It should have been included with our previous pull-request, but I did see the message in my queue until too late.
The following changes since commit 52ff8e91f916fa05dd47b5c30afa3286c30db444:
Merge tag 'nvme-6.12-2024-11-07' of git://git.infradead.org/nvme into block-6.12 (2024-11-07 13:57:12 -0700)
are available in the Git repository at:
git://git.infradead.org/nvme.git tags/nvme-6.12-2024-11-14
for you to fetch changes up to f0f5b364d903a35c02432b0f55d3a0114ba35845:
nvme/multipath: Fix RCU list traversal to use SRCU primitive (2024-11-07 13:40:59 -0800)
----------------------------------------------------------------
nvme fixes for Linux 6.12
- Use correct list traversal for srcu lists (Breno)
----------------------------------------------------------------
Breno Leitao (1):
nvme/multipath: Fix RCU list traversal to use SRCU primitive
drivers/nvme/host/multipath.c | 21 ++++++++++++++------- 1 file changed, 14 insertions(+), 7 deletions(-)
Jens Axboe
maintainerQuoted 3 lines · Keith Busch
Same fix as the last week's nvme fix, but for nvme-multipath. It should have been included with our previous pull-request, but I did see the message in my queue until too late.
Just to avoid yet another merge conflict, can we please just push this to 6.13 instead and just mark it stable? We probably should've done that with the other one as well, it's not like they are important fixes.
Signature · 1 line
Jens Axboe
Keith Busch
maintainerQuoted 8 lines · Jens Axboe
Quoted 3 lines · Keith Busch
Same fix as the last week's nvme fix, but for nvme-multipath. It should have been included with our previous pull-request, but I did see the message in my queue until too late.
Just to avoid yet another merge conflict, can we please just push this to 6.13 instead and just mark it stable? We probably should've done that with the other one as well, it's not like they are important fixes.
I was sending this now because I thought it would make it easier for stable to pick up without having to back out unrelated 6.13 conflicts. I just tried to merge upstream with this and block-6.13, and it actually looks like there aren't any conflicts anywa, so it doesn't matter.
So yes, let's drop this and I'll send it with the next nvme-6.13 pull request next week.
Jens Axboe
maintainerQuoted 10 lines · Keith Busch
Quoted 8 lines · Jens Axboe
Quoted 3 lines · Keith Busch
Same fix as the last week's nvme fix, but for nvme-multipath. It should have been included with our previous pull-request, but I did see the message in my queue until too late.
Just to avoid yet another merge conflict, can we please just push this to 6.13 instead and just mark it stable? We probably should've done that with the other one as well, it's not like they are important fixes.
Quoted 7 lines
I was sending this now because I thought it would make it easier for stable to pick up without having to back out unrelated 6.13 conflicts. I just tried to merge upstream with this and block-6.13, and it actually looks like there aren't any conflicts anywa, so it doesn't matter.
So yes, let's drop this and I'll send it with the next nvme-6.13 pull request next week.
OK if it merges cleanly, then we may as well do it. I'll check in a second.
Signature · 1 line
Jens Axboe