From: Aaron Tomlin <atomlin@atomlin.com>
To: steved@redhat.com, tbecker@redhat.com
Cc: yi.zhang@redhat.com, linux-nfs@vger.kernel.org
Subject: [PATCH 0/2] nfsrahead: fix uninitialised memory crash and refine fast-path logging
Date: Mon, 9 Mar 2026 10:50:23 -0400 [thread overview]
Message-ID: <20260309145025.107623-1-atomlin@atomlin.com> (raw)
Hi Steve, Yi,
This series addresses two issues stemming from the recent fast-path
optimisation used to reject non-NFS block devices, which were caught during
blktests.
1. [PATCH 1/2] fixes the glibc abort(3) by explicitly
zero-initialising the device_info struct. This prevents the cleanup
path from attempting to free uninitialised stack memory when the
fast-path triggers an early exit.
2. [PATCH 2/2] updates the error handling in main() to log a
descriptive debug message rather than a general error when a device
is intentionally skipped, preventing misleading udev journal spam.
Aaron Tomlin (2):
nfsrahead: zero-initialise device_info struct
nfsrahead: quieten misleading error for non-NFS block devices
tools/nfsrahead/main.c | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
--
2.51.0
next reply other threads:[~2026-03-09 14:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 14:50 Aaron Tomlin [this message]
2026-03-09 14:50 ` [PATCH 1/2] nfsrahead: zero-initialise device_info struct Aaron Tomlin
2026-03-09 14:50 ` [PATCH 2/2] nfsrahead: quieten misleading error for non-NFS block devices Aaron Tomlin
2026-03-11 8:27 ` [PATCH 0/2] nfsrahead: fix uninitialised memory crash and refine fast-path logging Yi Zhang
2026-03-11 16:11 ` Steve Dickson
2026-03-11 19:45 ` Aaron Tomlin
2026-03-12 12:50 ` Steve Dickson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260309145025.107623-1-atomlin@atomlin.com \
--to=atomlin@atomlin.com \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@redhat.com \
--cc=tbecker@redhat.com \
--cc=yi.zhang@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox