From: Christoph Hellwig <hch@infradead.org>
To: NeilBrown <neilb@suse.de>
Cc: Trond Myklebust <trond.myklebust@hammerspace.com>,
Anna Schumaker <anna@kernel.org>,
james.clark@arm.com, ltp@lists.linux.it, broonie@kernel.org,
Aishwarya.TCV@arm.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] NFS: abort nfs_atomic_open_v23 if name is too long.
Date: Tue, 28 May 2024 23:25:27 -0700 [thread overview]
Message-ID: <ZlbKVyVIJjh-_pUD@infradead.org> (raw)
In-Reply-To: <171693789645.27191.13475059024941012614@noble.neil.brown.name>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
prev parent reply other threads:[~2024-05-29 6:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 23:11 [PATCH] NFS: abort nfs_atomic_open_v23 if name is too long NeilBrown
2024-05-29 6:25 ` Christoph Hellwig [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=ZlbKVyVIJjh-_pUD@infradead.org \
--to=hch@infradead.org \
--cc=Aishwarya.TCV@arm.com \
--cc=anna@kernel.org \
--cc=broonie@kernel.org \
--cc=james.clark@arm.com \
--cc=linux-nfs@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=neilb@suse.de \
--cc=trond.myklebust@hammerspace.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