On Fri, Aug 02, 2019 at 09:44:20PM +0200, Miklos Szeredi wrote: > On Fri, Aug 2, 2019 at 10:15 AM Greg Kroah-Hartman > <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > > > > 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@xxxxxxxx> wrote: > > > > > > > > On Sun, Dec 30, 2018 at 10:52 AM Andreas Steinmetz <ast@xxxxxxxx> 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? > > Apparently yes, in v4.20.8 (f191c028cc33). No other kernel was > affected, AFAICS. Wonderful, thanks for letting me know. greg k-h
