From: owner@bugs.debian.org
This is a multi-part message in MIME format...
Your message dated Wed, 04 Feb 2026 08:22:23 +0000
with message-id
and subject line Bug#1122521: fixed in linux 6.18.8-1
has caused the Debian Bug report #1122521,
regarding linux-image-6.17.11+deb14-amd64: nvmet_rdma causes null pointer
dereference
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
1122521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1122521
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
Received: (at submit) by bugs.debian.org; 11 Dec 2025 04:48:49 +0000
X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02
(2024-03-25) on buxtehude.debian.org
X-Spam-Level:
X-Spam-Status: No, score=-9.0 required=4.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FOURLA,FVGT_m_MULTI_ODD,
HAS_PACKAGE,RCVD_IN_DNSWL_MED,RCVD_IN_VALIDITY_CERTIFIED_BLOCKED,
RCVD_IN_VALIDITY_RPBL_BLOCKED,RCVD_IN_VALIDITY_SAFE_BLOCKED,
SPF_HELO_PASS,SPF_PASS,WORD_WITHOUT_VOWELS autolearn=ham
autolearn_force=no version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 470; hammy, 150; neutral, 1011; spammy,
0. spammytokens: hammytokens:0.000-+--XDebbugsCc,
0.000-+--X-Debbugs-Cc, 0.000-+--rfkill, 0.000-+--devsel, 0.000-+--0c03
Return-path:
Received: from haruka.email ([172.104.100.164]:42410)
by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_X25519__RSA_P
S_RSAE_SHA256__AES_256_GCM:256)
(Exim 4.96)
(envelope-from )
id 1vTYbg-007rNd-13
for submit@bugs.debian.org;
Thu, 11 Dec 2025 04:48:49 +0000
Received: from [127.0.0.1] (localhost [127.0.0.1]) by localhost (Mailerdaemon)
with ESMTPSA id 8AC67213B46
for ; Thu, 11 Dec 2025 13:48:36 +0900 (JST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hcc.im; s=dkim;
t=1765428517;
h=from:reply-to:subject:date:message-id:to:mime-version:content-type:
content-transfer-encoding:content-language:in-reply-to:references:autocrypt;
bh=JdCbB6vvmodgohIT6iVFRrvc+8h5P4BqTj5A+UiFyrQ=;
b=qkIZrfU+gCIe3lzRsWEw20dId5736Kef/bZ/qq2wo+d/XBp3XvtmIzORGBWG8OiK6fUnqJ
PMo3+UQ+uMFYXC5Mq8JU456NRzW9RR4FsDbUscsxqiUFo8E4psxT9I/xIgaQRue7plfxNQ
6aiwXIHLl/eNIbQNbnXCa27h0VuAOuA=
Message-ID:
Date: Thu, 11 Dec 2025 13:48:35 +0900
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
From: Haruka Ma
Subject: linux-image-6.17.11+deb14-amd64: nvmet_rdma causes null pointer
dereference
Reply-To: Haruka Ma
References: <>
Content-Language: en-US
To: submit@bugs.debian.org
Autocrypt: addr=mrx@hcc.im; keydata=
xjMEV4kOzRYJKwYBBAHaRw8BAQdAuNZ0N+G1yAmNkLP7n5QqFUhWtm5ICaWwTcZC6LawgFLN
FkhhcnVrYSBNYSA8bXJ4QGhjYy5pbT7CkAQTFgoAOBYhBBt4nlrys+MVz6tB4RYZIJYAIAU2
BQJY/cLQAhsjBQsJCAcDBRUKCQgLBRYCAwEAAh4BAheAAAoJEBYZIJYAIAU2pycBALbAvTY7
VdhOmY0wic9w9tsR6cj5X/mBVEkZB8uvSMzzAP4sTQCSalreZiVi5KdSgWIIlYdsl8HN6nZs
TXxDY4tOC844BFeLPnYSCisGAQQBl1UBBQEBB0BW59Z3UcCY26EUqXVogm0rVHWM12fns2Du
iCc8raloVAMBCAfCYQQYFgoACQUCV4s+dgIbDAAKCRAWGSCWACAFNlg9AP9+x+WiruAXztYB
WzU00+boXQXuDplrIEpqfyXPYCzPTAD/Rw5ecq41IltCBGUVaXW1eyfAkXvcOXQPJfoLYPCH BAE=
In-Reply-To: <>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Last-TLS-Session-Version: TLSv1.3
Delivered-To: submit@bugs.debian.org
Package: src:linux
Version: 6.17.11-1
Severity: normal
X-Debbugs-Cc: none
I'm using ZFS on my storage server and mounting 2 zvols on a remote
machine via nvmet_rdma. I can't pinpoint the version, but after I once
rebooted the server and started running on a new kernel, after running
the server for a while, there will be a null pointer dereference
apparently caused by nvmet_rdma (see kernel log below). It's a very hard
to recover from this situation as the transport is supposed to be
reliable and any packet loss would cause kernel lock-ups on the
initiator side.
It seems to me that this is likely a kernel issue. I haven't tried if
disabling cgroup io / blkio would avoid this. As the issue only appears
after hours or days of using the block device, it's currently hard for
me to bisect kernel versions, as I need to at least reboot one machine
to recover and it's kinda disruptive.
The taints are because of loading ZFS, unfortunately due to how the
storage system is designed, it's impossible for me to reproduce this
without kernel taints.
reportbug output below (redacted network information):
-- Package-specific info:
** Version:
Linux version 6.17.11+deb14-amd64 (debian-kernel@lists.debian.org)
(x86_64-linux-gnu-gcc-15 (Debian 15.2.0-10) 15.2.0, GNU ld (GNU Binutils
for Debian) 2.45.50.20251201) #1 SMP PREEMPT_DYNAMIC Debian 6.17.11-1
(2025-12-07)
** Command line:
BOOT_IMAGE=/boot@/vmlinuz-6.17.11+deb14-amd64 root=ZFS=root/root ro
root=ZFS=root/root mitigations=off
** Tainted: PDWOE (12929)
* proprietary module was loaded
* kernel died recently, i.e. there was an OOPS or BUG
* kernel issued warning
[continued in next message]
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
