linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miklos Szeredi <miklos@szeredi.hu>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: Chirantan Ekbote <chirantan@chromium.org>,
	linux-fsdevel@vger.kernel.org, Dylan Reid <dgreid@chromium.org>,
	Suleiman Souhlal <suleiman@chromium.org>,
	fuse-devel <fuse-devel@lists.sourceforge.net>
Subject: Re: [PATCH] fuse: Fix parameter for FS_IOC_{GET,SET}FLAGS
Date: Thu, 16 Jul 2020 07:17:35 +0200	[thread overview]
Message-ID: <CAJfpegvG+xMNaL4r1UATGu6tjZqjapp50=Z4rsq6sumaBzwFMQ@mail.gmail.com> (raw)
In-Reply-To: <CA+icZUWDtOHpgTCEhPatYfR+zJAbOBK2ihtf7G=zzCKAxiVmsQ@mail.gmail.com>

On Thu, Jul 16, 2020 at 1:06 AM Sedat Dilek <sedat.dilek@gmail.com> wrote:
>
> On Wed, Jul 15, 2020 at 5:05 PM Miklos Szeredi <miklos@szeredi.hu> wrote:
> >
> > On Tue, Jul 14, 2020 at 12:26 PM Chirantan Ekbote
> > <chirantan@chromium.org> wrote:
> > >
> > > The ioctl encoding for this parameter is a long but the documentation
> > > says it should be an int and the kernel drivers expect it to be an int.
> > > If the fuse driver treats this as a long it might end up scribbling over
> > > the stack of a userspace process that only allocated enough space for an
> > > int.
> > >
> > > This was previously discussed in [1] and a patch for fuse was proposed
> > > in [2].  From what I can tell the patch in [2] was nacked in favor of
> > > adding new, "fixed" ioctls and using those from userspace.  However
> > > there is still no "fixed" version of these ioctls and the fact is that
> > > it's sometimes infeasible to change all userspace to use the new one.
> >
> > Okay, applied.
> >
>
> ...and pushed? I do not see in in fuse.git.

Pushed now.

Thanks,
Miklos

      reply	other threads:[~2020-07-16  5:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-14 10:26 [PATCH] fuse: Fix parameter for FS_IOC_{GET,SET}FLAGS Chirantan Ekbote
2020-07-15 12:20 ` Miklos Szeredi
2020-07-15 23:06   ` Sedat Dilek
2020-07-16  5:17     ` Miklos Szeredi [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='CAJfpegvG+xMNaL4r1UATGu6tjZqjapp50=Z4rsq6sumaBzwFMQ@mail.gmail.com' \
    --to=miklos@szeredi.hu \
    --cc=chirantan@chromium.org \
    --cc=dgreid@chromium.org \
    --cc=fuse-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=sedat.dilek@gmail.com \
    --cc=suleiman@chromium.org \
    /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).