From: Markus Elfring <Markus.Elfring@web.de>
To: vulab@iscas.ac.cn, linux-nfs@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
Anna Schumaker <anna@kernel.org>,
Trond Myklebust <trondmy@kernel.org>
Subject: Re: [PATCH] NFS: handle wait_on_bit_action() errors in nfs_vm_page_mkwrite()
Date: Fri, 7 Mar 2025 18:29:02 +0100 [thread overview]
Message-ID: <03bc1b71-6b53-428e-8b2e-4f3a434087b1@web.de> (raw)
In-Reply-To: <20250303140314.1650-1-vulab@iscas.ac.cn>
> Add error handling for wait_on_bit_action() failures in the page
> fault path. Return VM_FAULT_SIGBUS instead of proceeding with
> folio operations when wait_on_bit_action() fails.
call failed?
How do you think about to add any tags (like “Fixes” and “Cc”) accordingly?
https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.14-rc5#n145
Regards,
Markus
prev parent reply other threads:[~2025-03-07 17:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 14:03 [PATCH] NFS: handle wait_on_bit_action() errors in nfs_vm_page_mkwrite() Wentao Liang
2025-03-07 17:29 ` Markus Elfring [this message]
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=03bc1b71-6b53-428e-8b2e-4f3a434087b1@web.de \
--to=markus.elfring@web.de \
--cc=anna@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@kernel.org \
--cc=vulab@iscas.ac.cn \
/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