[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <27a45b25-98ba-4229-a257-2d29c88d975c@web.de>
Date: Sun, 12 Oct 2025 13:21:23 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Baolin Liu <liubaolin@...inos.cn>, linux-nfs@...r.kernel.org,
Anna Schumaker <anna@...nel.org>, Trond Myklebust <trondmy@...nel.org>
Cc: Baolin Liu <liubaolin12138@....com>, LKML <linux-kernel@...r.kernel.org>,
kernel-janitors@...r.kernel.org
Subject: Re: [PATCH] NFS: Fix possible NULL pointer dereference in
nfs_inode_remove_request()
…
> 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
Powered by blists - more mailing lists