Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <1585733475-5222-1-git-send-email-chakragithub@gmail.com>
 <CAJfpegtk=pbLgBzM92tRq8UMUh+vxcDcwLL77iAcv=Mxw3r4Lw@mail.gmail.com> <CAH7=fosGV3AOcU9tG0AK3EJ2yTXZL3KGfsuVUA5gMBjC4Nn-WQ@mail.gmail.com>
In-Reply-To: <CAH7=fosGV3AOcU9tG0AK3EJ2yTXZL3KGfsuVUA5gMBjC4Nn-WQ@mail.gmail.com>
From:   Chakra Divi <chakragithub@gmail.com>
Date:   Mon, 27 Apr 2020 19:16:08 +0530
Message-ID: <CAH7=fosz9KDSBN86+7OxYTLJWUSdUSkeLZR5Y0YyM6=GE0BdOw@mail.gmail.com>
Subject: Re: [PATCH] fuse:rely on fuse_perm for exec when no mode bits set
To:     Miklos Szeredi <miklos@szeredi.hu>
Cc:     linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Tue, Apr 21, 2020 at 4:21 PM Chakra Divi <chakragithub@gmail.com> wrote:
>
> On Mon, Apr 20, 2020 at 4:55 PM Miklos Szeredi <miklos@szeredi.hu> wrote:
> >
> > On Wed, Apr 1, 2020 at 11:31 AM Chakra Divi <chakragithub@gmail.com> wrote:
> > >
> > > In current code, for exec we are checking mode bits
> > > for x bit set even though the fuse_perm_getattr returns
> > > success. Changes in this patch avoids mode bit explicit
> > > check, leaves the exec checking to fuse file system
> > > in uspace.
> >
> > Why is this needed?
>
> Thanks for responding Miklos. We have an use case with our remote file
> system mounted on fuse , where permissions checks will happen remotely
> without the need of mode bits. In case of read, write it worked
> without issues. But for executable files, we found that fuse kernel is
> explicitly checking 'x' mode bit set on the file. We want this
> checking also to be pushed to remote instead of kernel doing it - so
> modified the kernel code to send getattr op to usespace in exec case
> too.

Any help on this Miklos....

Thanks,
Chakra
> > Thanks,
> > Miklos