mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ChenXiaoSong <chenxiaosong2@huawei.com>
To: <trond.myklebust@hammerspace.com>, <anna@kernel.org>
Cc: <linux-nfs@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<yi.zhang@huawei.com>, <zhangxiaoxu5@huawei.com>
Subject: Re: [PATCH v3 0/2] NFS: check FMODE_EXEC from open context mode
Date: Mon, 10 Oct 2022 09:18:13 +0800	[thread overview]
Message-ID: <c57c461e-1e4a-e0fd-177b-af4943df1aca@huawei.com> (raw)
In-Reply-To: <20220923054015.2890271-1-chenxiaosong2@huawei.com>

Friendly ping...

在 2022/9/23 13:40, ChenXiaoSong 写道:
> Currently, we check FMODE_EXEC from file f_flags, and check FMODE_READ or
> FMODE_WRITE from open context mode.
> 
> After converting file f_flags to open context mode by flags_to_mode(),
> we can check all mode from open context mode.
> 
> ChenXiaoSong (2):
>    NFS: make sure open context mode have FMODE_EXEC when file open for
>      exec
>    NFSv4: check FMODE_EXEC from open context mode in
>      nfs4_opendata_access()
> 
>   fs/nfs/inode.c    |  3 ++-
>   fs/nfs/nfs4file.c | 12 ++++--------
>   fs/nfs/nfs4proc.c | 16 +++++-----------
>   3 files changed, 11 insertions(+), 20 deletions(-)
> 

  parent reply	other threads:[~2022-10-10  1:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23  5:40 ChenXiaoSong
2022-09-23  5:40 ` [PATCH v3 1/2] NFS: make sure open context mode have FMODE_EXEC when file open for exec ChenXiaoSong
2022-09-23  5:40 ` [PATCH v3 2/2] NFSv4: check FMODE_EXEC from open context mode in nfs4_opendata_access() ChenXiaoSong
2022-10-10  1:18 ` ChenXiaoSong [this message]
2022-11-16 11:45 ` [PATCH v3 0/2] NFS: check FMODE_EXEC from open context mode ChenXiaoSong

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=c57c461e-1e4a-e0fd-177b-af4943df1aca@huawei.com \
    --to=chenxiaosong2@huawei.com \
    --cc=anna@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@hammerspace.com \
    --cc=yi.zhang@huawei.com \
    --cc=zhangxiaoxu5@huawei.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
all inboxes | Powered by JetHome®