messages from 2025-11-25 05:01:00 to 2025-12-01 18:36:41 UTC [more...]
[PATCH 0/4] block: add IOC_PR_READ_KEYS and IOC_PR_READ_RESERVATION ioctls
2025-12-01 18:36 UTC (17+ messages)
` [PATCH 1/4] scsi: sd: reject invalid pr_read_keys() num_keys values
` [PATCH 2/4] nvme: "
` [PATCH 3/4] block: add IOC_PR_READ_KEYS ioctl
` [PATCH 4/4] block: add IOC_PR_READ_RESERVATION ioctl
[PATCHv2] nvme-tcp: Implement recvmsg() receive flow
2025-12-01 17:49 UTC (13+ messages)
[PATCHv2 0/9] nvme-auth: switch to use the kernel keyring
2025-12-01 17:02 UTC (31+ messages)
` [PATCH 1/9] nvme-auth: modify nvme_auth_transform_key() to return status
` [PATCH 2/9] nvme-keyring: add 'dhchap' key type
` [PATCH 3/9] nvme-auth: switch to use 'struct key'
` [PATCH 4/9] nvme: parse dhchap keys during option parsing
` [PATCH 5/9] nvmet-auth: parse dhchap key from configfs attribute
` [PATCH 6/9] nvme: allow to pass in key description as dhchap secret
` [PATCH 7/9] nvme-auth: wait for authentication to finish when changing keys
` [PATCH 8/9] nvme-fabrics: allow to pass in keyring by name
` [PATCH 9/9] nvmet: add configfs attribute 'dhchap_keyring'
[PATCH v2 0/4] block: add IOC_PR_READ_KEYS and IOC_PR_READ_RESERVATION ioctls
2025-12-01 16:33 UTC (19+ messages)
` [PATCH v2 1/4] scsi: sd: reject invalid pr_read_keys() num_keys values
` [PATCH v2 2/4] nvme: "
` [PATCH v2 3/4] block: add IOC_PR_READ_KEYS ioctl
` [PATCH v2 4/4] block: add IOC_PR_READ_RESERVATION ioctl
[PATCH v5 0/6] nvme-tcp: Support receiving KeyUpdate requests
2025-12-01 15:03 UTC (21+ messages)
` [PATCH v5 1/6] net/handshake: Store the key serial number on completion
` [PATCH v5 2/6] net/handshake: Define handshake_sk_destruct_req
` [PATCH v5 4/6] net/handshake: Support KeyUpdate message types
` [PATCH v5 5/6] nvme-tcp: Support KeyUpdate
WD Red SN700 4000GB, F/W: 11C120WD (Device not ready; aborting reset, CSTS=0x1)
2025-12-01 14:16 UTC (13+ messages)
[PATCH v2 00/12] Fix bio chain related issues
2025-12-01 10:31 UTC (27+ messages)
` [PATCH v2 01/12] block: fix incorrect logic in bio_chain_endio
` [PATCH v2 02/12] block: prevent race condition on bi_status in __bio_chain_endio
` [PATCH v2 03/12] md: bcache: fix improper use of bi_end_io
` [PATCH v2 04/12] block: prohibit calls to bio_chain_endio
` [PATCH v2 05/12] block: export bio_chain_and_submit
` [PATCH v2 06/12] gfs2: Replace the repetitive bio chaining code patterns
` [PATCH v2 07/12] xfs: "
` [PATCH v2 08/12] block: "
` [PATCH v2 09/12] fs/ntfs3: "
` [PATCH v2 10/12] zram: "
` [PATCH v2 11/12] nvdimm: "
` [PATCH v2 12/12] nvmet: use bio_chain_and_submit to simplify bio chaining
[PATCH v2] nvme: nvme_identify_ns_descs: prevent oob
2025-12-01 6:21 UTC (2+ messages)
[PATCH v2 0/1] nvme: Convert tag_list mutex to rwsemaphore to avoid deadlock
2025-12-01 2:50 UTC (7+ messages)
` [PATCH v2 1/1] "
[PATCH] nvme: fix admin request_queue lifetime
2025-11-30 23:16 UTC (2+ messages)
[PATCH V2] nvme: expose active quirks in sysfs
2025-11-30 23:09 UTC (2+ messages)
[PATCH 1/1] nvme-fabrics: add ENOKEY to no retry criteria for authentication failures
2025-11-30 23:05 UTC (7+ messages)
[PATCH] nvme-auth: Use kvfree() for memory allocated with kvcalloc()
2025-11-30 22:53 UTC (2+ messages)
[PATCH 1/2] nvmet-rdma: Use kvcalloc for commands and responses arrays
2025-11-30 22:52 UTC (4+ messages)
` [PATCH 2/2] nvmet-tcp: Use kvcalloc for commands array
[PATCH V2] nvme-tcp: use __fput_sync() to avoid use-after-free on reset
2025-11-30 22:51 UTC (3+ messages)
[PATCH] nvme: nvme_identify_ns_descs: prevent oob
2025-11-30 22:20 UTC (6+ messages)
Fix potential data loss and corruption due to Incorrect BIO Chain Handling
2025-11-28 6:26 UTC (16+ messages)
` [PATCH 1/9] block: fix data loss and stale date exposure problems during append write
[linux-nvme:nvme-6.19] BUILD SUCCESS WITH WARNING db2792e1d7696594dcd09dcc97f262e69819a820
2025-11-26 20:32 UTC
[PATCH V3 0/6] block: ignore __blkdev_issue_discard() ret value
2025-11-26 10:37 UTC (24+ messages)
` [PATCH V3 1/6] block: ignore discard return value
` [PATCH V3 4/6] nvmet: "
` [f2fs-dev] "
` [PATCH V3 5/6] f2fs: "
` [PATCH V3 6/6] xfs: "
` [f2fs-dev] "
` (subset) [PATCH V3 0/6] block: ignore __blkdev_issue_discard() ret value
[PATCH V2 0/5] block: ignore __blkdev_issue_discard() ret value
2025-11-26 9:26 UTC (6+ messages)
` [PATCH V2 1/5] block: ignore discard return value
` [PATCH V2 2/5] dm: "
Pytanie o samochód
2025-11-26 9:00 UTC
[PATCH] nvmet-auth: update sc_c in host response
2025-11-26 7:16 UTC (2+ messages)
[PATCH 00/44] Change a lot of min_t() that might mask high bits
2025-11-24 9:49 UTC (2+ messages)
[RFC PATCH 00/14] TP8028 Rapid Path Failure Recovery
2025-11-26 2:12 UTC (15+ messages)
` [RFC PATCH 01/14] nvmet: Rapid Path Failure Recovery set controller identify fields
` [RFC PATCH 02/14] nvmet/debugfs: Add ctrl uniquifier and random values
` [RFC PATCH 03/14] nvmet: Implement CCR nvme command
` [RFC PATCH 04/14] nvmet: Implement CCR logpage
` [RFC PATCH 05/14] nvmet: Send an AEN on CCR completion
` [RFC PATCH 06/14] nvme: Rapid Path Failure Recovery read controller identify fields
` [RFC PATCH 07/14] nvme: Add RECOVERING nvme controller state
` [RFC PATCH 08/14] nvme: Implement cross-controller reset recovery
` [RFC PATCH 09/14] nvme: Implement cross-controller reset completion
` [RFC PATCH 10/14] nvme-tcp: Use CCR to recover controller that hits an error
` [RFC PATCH 11/14] nvme-rdma: "
` [RFC PATCH 12/14] nvme-fc: Decouple error recovery from controller reset
` [RFC PATCH 13/14] nvme-fc: Use CCR to recover controller that hits an error
` [RFC PATCH 14/14] nvme-fc: Hold inflight requests while in RECOVERING state
[linux-nvme:nvme-6.19 3/27] include/linux/kern_levels.h:5:25: warning: format '%ld' expects argument of type 'long int', but argument 2 has type 'size_t' {aka 'unsigned int'}
2025-11-25 21:19 UTC
[RFC v2 00/11] Add dmabuf read/write via io_uring
2025-11-25 19:40 UTC (9+ messages)
[RFC blktests fix PATCH] tcp: use GFP_ATOMIC in tcp_disconnect
2025-11-25 12:33 UTC (10+ messages)
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox