linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Steinmetz <ast@domdv.de>
To: linux-fsdevel@vger.kernel.org
Subject: [PATCH] Fix cuse ENOMEM ioctl breakage in 4.20.0
Date: Sun, 30 Dec 2018 10:43:47 +0100	[thread overview]
Message-ID: <1546163027.3036.2.camel@domdv.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 295 bytes --]

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.
-- 
Andreas Steinmetz                       SPAMmers use robotrap@domdv.de

[-- Attachment #2: cuse-4.20.0.patch --]
[-- Type: text/x-patch, Size: 424 bytes --]

--- linux.orig/fs/fuse/cuse.c	2018-12-30 09:52:47.479717022 +0100
+++ linux/fuse/cuse.c	2018-12-30 09:53:22.944128852 +0100
@@ -324,6 +324,7 @@
 	fc->minor = arg->minor;
 	fc->max_read = max_t(unsigned, arg->max_read, 4096);
 	fc->max_write = max_t(unsigned, arg->max_write, 4096);
+	fc->max_pages = FUSE_DEFAULT_MAX_PAGES_PER_REQ;
 
 	/* parse init reply */
 	cc->unrestricted_ioctl = arg->flags & CUSE_UNRESTRICTED_IOCTL;

             reply	other threads:[~2018-12-30  9:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-30  9:43 Andreas Steinmetz [this message]
2019-01-14  9:58 ` [PATCH] Fix cuse ENOMEM ioctl breakage in 4.20.0 Miklos Szeredi
     [not found]   ` <388f911ccba16dee350bb2534b67d601b44f3a92.camel@domdv.de>
2019-05-28 13:12     ` Miklos Szeredi
2019-08-02  8:15       ` Greg Kroah-Hartman
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=1546163027.3036.2.camel@domdv.de \
    --to=ast@domdv.de \
    --cc=linux-fsdevel@vger.kernel.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).