From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Andreas Steinmetz <ast@domdv.de>, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] Fix cuse ENOMEM ioctl breakage in 4.20.0
Date: Fri, 2 Aug 2019 10:15:01 +0200 [thread overview]
Message-ID: <20190802081501.GK26174@kroah.com> (raw)
In-Reply-To: <CAJfpegtQ11yRhg3+h+dCJ_juc6KGKBLLwB_Vco8+KDACpBmY5w@mail.gmail.com>
On Tue, May 28, 2019 at 03:12:28PM +0200, Miklos Szeredi wrote:
> On Sat, May 18, 2019 at 3:58 PM Andreas Steinmetz <ast@domdv.de> wrote:
>
> > > On Sun, Dec 30, 2018 at 10:52 AM Andreas Steinmetz <ast@domdv.de> wrote:
> > > > This must have happened somewhen after 4.17.2 and I did find it in
> > > > 4.20.0:
> > > >
> > > > cuse_process_init_reply() doesn't initialize fc->max_pages and thus all
> > > > cuse bases ioctls fail with ENOMEM.
> > > >
> > > > Patch which fixes this is attached.
> > >
> > > Thanks. Pushed a slightly different patch:
> > >
> > > https://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git/commit/?h=for-next&id=666a40e87038221d45d47aa160b26410fd67c1d2
> > >
>
> > It got broken again, ENONEM.
> > I do presume that commit 5da784cce4308ae10a79e3c8c41b13fb9568e4e0 is the
> > culprit. Could you please fix this and, please, could somebody do a cuse
> > regression test after changes to fuse?
>
> Hi,
>
> Can you please tell us which kernel is broken?
Did this ever get resolved?
totally confused,
greg k-h
next prev parent reply other threads:[~2019-08-02 8:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-30 9:43 [PATCH] Fix cuse ENOMEM ioctl breakage in 4.20.0 Andreas Steinmetz
2019-01-14 9:58 ` Miklos Szeredi
[not found] ` <388f911ccba16dee350bb2534b67d601b44f3a92.camel@domdv.de>
2019-05-28 13:12 ` Miklos Szeredi
2019-08-02 8:15 ` Greg Kroah-Hartman [this message]
2019-08-02 19:44 ` Miklos Szeredi
2019-08-03 6:47 ` Greg Kroah-Hartman
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=20190802081501.GK26174@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ast@domdv.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.