From: Markus Elfring <Markus.Elfring@web.de>
To: Baolin Liu <liubaolin@kylinos.cn>,
linux-nfs@vger.kernel.org, Anna Schumaker <anna@kernel.org>,
Trond Myklebust <trondmy@kernel.org>
Cc: Baolin Liu <liubaolin12138@163.com>,
LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] NFS: Fix possible NULL pointer dereference in nfs_inode_remove_request()
Date: Sun, 12 Oct 2025 13:21:23 +0200 [thread overview]
Message-ID: <27a45b25-98ba-4229-a257-2d29c88d975c@web.de> (raw)
In-Reply-To: <20251012083957.532330-1-liubaolin12138@163.com>
…
> Fix this by checking folio before using it or calling
> folio_end_dropbehind().
How do you think about to add any tags (like “Fixes” and “Cc”) accordingly?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.17#n145
…
> ---
> fs/nfs/write.c | 11 ++++++-----
…
Can a summary phrase like “Prevent null pointer dereference in nfs_inode_remove_request()”
be nicer?
Will development interests grow for the application of scope-based resource management?
https://elixir.bootlin.com/linux/v6.17.1/source/include/linux/spinlock.h#L565-L567
Regards,
Markus
next prev parent reply other threads:[~2025-10-12 11:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-12 8:39 [PATCH v1] " Baolin Liu
2025-10-12 11:21 ` Markus Elfring [this message]
2025-10-13 4:47 ` Trond Myklebust
2025-10-17 6:57 ` liubaolin
2025-10-17 15:02 ` Trond Myklebust
2025-10-22 2:44 ` liubaolin
2025-10-22 3:15 ` Trond Myklebust
2025-10-22 3:26 ` Trond Myklebust
2025-10-22 7:34 ` Dan Carpenter
2025-10-22 7:36 ` Dan Carpenter
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=27a45b25-98ba-4229-a257-2d29c88d975c@web.de \
--to=markus.elfring@web.de \
--cc=anna@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=liubaolin12138@163.com \
--cc=liubaolin@kylinos.cn \
--cc=trondmy@kernel.org \
/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
all inboxes | Powered by JetHome®