From: "Mkrtchyan, Tigran" <tigran.mkrtchyan@desy.de>
To: Benjamin Coddington <bcodding@redhat.com>
Cc: Trond Myklebust <trondmy@hammerspace.com>, anna <anna@kernel.org>,
linux-nfs <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] nfs4: don't map EACCESS and EPERM to EIO
Date: Tue, 13 Jun 2023 10:27:37 +0200 (CEST) [thread overview]
Message-ID: <1588974117.1198850.1686644857335.JavaMail.zimbra@desy.de> (raw)
In-Reply-To: <83016291-825A-4A16-B7A8-8B492A47CD5A@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 732 bytes --]
Thanks, Ben!
Tigran.
----- Original Message -----
> From: "Benjamin Coddington" <bcodding@redhat.com>
> To: "Tigran Mkrtchyan" <tigran.mkrtchyan@desy.de>
> Cc: "Trond Myklebust" <trondmy@hammerspace.com>, "anna" <anna@kernel.org>, "linux-nfs" <linux-nfs@vger.kernel.org>
> Sent: Friday, 9 June, 2023 16:00:34
> Subject: Re: [PATCH] nfs4: don't map EACCESS and EPERM to EIO
> On 9 Jun 2023, at 9:30, Mkrtchyan, Tigran wrote:
>
>> Hi Trond,
>>
>> Obviously, the patch is incorrect. The behavior of the upstream kernel and
>> RHEL kernels are different.
>
> RHEL-9 should be ok here.
>
> There's a few things we need to be fixing for RHEL-8.9. This is one of them.
> https://bugzilla.redhat.com/show_bug.cgi?id=2213828
>
> Ben
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2208 bytes --]
prev parent reply other threads:[~2023-06-13 8:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 14:49 [PATCH] nfs4: don't map EACCESS and EPERM to EIO Tigran Mkrtchyan
2023-06-08 15:33 ` Trond Myklebust
[not found] ` <AD6C85BF-50F9-42BB-83E8-16BCE03D3CF1@desy.de>
2023-06-08 17:53 ` Trond Myklebust
2023-06-09 13:30 ` Mkrtchyan, Tigran
2023-06-09 14:00 ` Benjamin Coddington
2023-06-13 8:27 ` Mkrtchyan, Tigran [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=1588974117.1198850.1686644857335.JavaMail.zimbra@desy.de \
--to=tigran.mkrtchyan@desy.de \
--cc=anna@kernel.org \
--cc=bcodding@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@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