Skip to content

Tags: longhorn/spdk

Tags

v25.09.0+4

Toggle v25.09.0+4's commit message
Automated tag creation: v25.09.0+4 for commit 440f107

v25.09.0+3

Toggle v25.09.0+3's commit message
Automated tag creation: v25.09.0+3 for commit 92048fc

v25.09.0+2

Toggle v25.09.0+2's commit message
Automated tag creation: v25.09.0+2 for commit 0c851e8

v25.09.0+1

Toggle v25.09.0+1's commit message
Automated tag creation: v25.09.0+1 for commit e1d5238

v24.09.0+6

Toggle v24.09.0+6's commit message
Automated tag creation: v24.09.0+6 for commit 084520c

v25.05.0+4

Toggle v25.05.0+4's commit message
bdev/nvme: fix GPT examination hang in interrupt mode

- Remove the dependency on global transport type (g_nvme_trtype).
- In interrupt mode, always enable periodic polling so TCP qpairs
  can process send/receive queues and complete I/O.

longhorn/longhorn-11816

Signed-off-by: Chin-Ya Huang <chin-ya.huang@suse.com>

v25.05.0+3

Toggle v25.05.0+3's commit message
bdev/nvme: allow global NVMe transport type overwrite

longhorn/longhorn-11761

Signed-off-by: Chin-Ya Huang <chin-ya.huang@suse.com>

v25.05.0+2

Toggle v25.05.0+2's commit message
bdev/raid: reset base bdev after quiesce to avoid UAF on removal

When an NVMe controller faults (fast-io-fail + reconnect), NVMe retry I/Os
may complete FAILED (propagated as ENXIO). RAID then schedules base-bdev
removal. During removal we quiesce the RAID bdev and the bdev layer starts
tearing down core channels. Later, while destroying module channels, the
NVMe module finishes aborting remaining retry I/Os; those completions
re-enter the RAID path and spdk_bdev_free_io() dereferences a core channel
that was already freed, causing a use-after-free.

Fix: spdk#3703
after the RAID bdev is quiesced, issue spdk_bdev_reset() to the base
bdev so outstanding I/Os are drained/aborted before core-channel resources
are released. Continue the existing removal flow only after reset
completion.

Change-Id: Ifa715c06ceecc8eed709e3049484eaf50663d9a0
Signed-off-by: jinhong.kim0 <jinhong.kim0@navercorp.com>
Reviewed-on: https://review.spdk.io/c/spdk/spdk/+/26443
Community-CI: Mellanox Build Bot
Reviewed-by: Shuhei Matsumoto <smatsumoto@nvidia.com>
Reviewed-by: Artur Paszkiewicz <artur.paszkiewicz@solidigm.com>
Tested-by: SPDK Automated Test System <spdkbot@gmail.com>
Reviewed-by: Jim Harris <jim.harris@nvidia.com>
(cherry picked from commit 607f670)

v25.05.0+1

Toggle v25.05.0+1's commit message
nvme/tcp: use async version of sock connect

Change-Id: I8a7a812ae56418f27a4f97ccc66f5d36e39ac01e
Signed-off-by: Jacek Kalwas <jacek.kalwas@nutanix.com>
Reviewed-on: https://review.spdk.io/c/spdk/spdk/+/26045
Reviewed-by: Tomasz Zawadzki <tomasz@tzawadzki.com>
Tested-by: SPDK Automated Test System <spdkbot@gmail.com>
Community-CI: Mellanox Build Bot
Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com>
Reviewed-by: Jim Harris <jim.harris@nvidia.com>

v24.09.0+5

Toggle v24.09.0+5's commit message
blob: don't delete checksums when parent detaching

When a snapshot is detached from its parent, its data do not change,
so we can keep the computed clusters checksums.

Longhorn 10037

Signed-off-by: Damiano Cipriani <damiano.cipriani@suse.com>