linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Miklos Szeredi <mszeredi@redhat.com>, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] fuse: allow O_PATH fd for FUSE_DEV_IOC_BACKING_OPEN
Date: Fri, 13 Sep 2024 13:44:23 +0200	[thread overview]
Message-ID: <CAOQ4uxgobGJMASEesrsCt447G_=sU5ompBvfq+Vrfc4Ag_aBYA@mail.gmail.com> (raw)
In-Reply-To: <CAJfpegsfrfwgqfeap7VkJkxsPzjW+WhjJqjYfDVyCa9WF-40Cg@mail.gmail.com>

On Fri, Sep 13, 2024 at 1:13 PM Miklos Szeredi <miklos@szeredi.hu> wrote:
>
> On Fri, 13 Sept 2024 at 13:05, Amir Goldstein <amir73il@gmail.com> wrote:
> >
> > On Fri, Sep 13, 2024 at 12:50 PM Miklos Szeredi <mszeredi@redhat.com> wrote:
>
> > > -       res = -EOPNOTSUPP;
> > > -       if (!file->f_op->read_iter || !file->f_op->write_iter)
> > > -               goto out_fput;
> > > -
> >
> > FWIW, I have made those sanity checks opt-in in my
> > fuse-backing-inode-wip branch:
> > https://github.com/amir73il/linux/commit/24c9a87bb11d76414b85960c0e3638a655a9c9a1
> >
> > But that could be added later.
>
> This is the wrong place to check the f_op.
>
> We could do it in backing_file_open(), but this isn't going to be a
> common error, so I guess just returning an error at read/write time is
> also okay.
>

Yeh. works for me.

Thanks,
Amir.

      reply	other threads:[~2024-09-13 11:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-13 10:47 [PATCH] fuse: allow O_PATH fd for FUSE_DEV_IOC_BACKING_OPEN Miklos Szeredi
2024-09-13 11:04 ` Amir Goldstein
2024-09-13 11:12   ` Miklos Szeredi
2024-09-13 11:44     ` Amir Goldstein [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='CAOQ4uxgobGJMASEesrsCt447G_=sU5ompBvfq+Vrfc4Ag_aBYA@mail.gmail.com' \
    --to=amir73il@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=mszeredi@redhat.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;
as well as URLs for NNTP newsgroup(s).