[Bug 1823972] Re: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

2021-04-06 Thread Po-Hsu Lin
** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823972

Title:
  bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823972/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1823972] Re: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

2019-06-02 Thread Kirill Smelkov
Thanks for fixing this issue. We confirm that the problem is gone with
updated kernel.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823972

Title:
  bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823972/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1823972] Re: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

2019-05-14 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.15.0-50.54

---
linux (4.15.0-50.54) bionic; urgency=medium

  * CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
- x86/cpu: Sanitize FAM6_ATOM naming
- kvm: x86: Report STIBP on GET_SUPPORTED_CPUID
- locking/atomics, asm-generic: Move some macros from  to a
  new  file
- tools include: Adopt linux/bits.h
- x86/msr-index: Cleanup bit defines
- x86/speculation: Consolidate CPU whitelists
- x86/speculation/mds: Add basic bug infrastructure for MDS
- x86/speculation/mds: Add BUG_MSBDS_ONLY
- x86/kvm: Expose X86_FEATURE_MD_CLEAR to guests
- x86/speculation/mds: Add mds_clear_cpu_buffers()
- x86/speculation/mds: Clear CPU buffers on exit to user
- x86/kvm/vmx: Add MDS protection when L1D Flush is not active
- x86/speculation/mds: Conditionally clear CPU buffers on idle entry
- x86/speculation/mds: Add mitigation control for MDS
- x86/speculation/mds: Add sysfs reporting for MDS
- x86/speculation/mds: Add mitigation mode VMWERV
- Documentation: Move L1TF to separate directory
- Documentation: Add MDS vulnerability documentation
- x86/speculation/mds: Add mds=full,nosmt cmdline option
- x86/speculation: Move arch_smt_update() call to after mitigation decisions
- x86/speculation/mds: Add SMT warning message
- x86/speculation/mds: Fix comment
- x86/speculation/mds: Print SMT vulnerable on MSBDS with mitigations off
- x86/speculation/mds: Add 'mitigations=' support for MDS

  * CVE-2017-5715 // CVE-2017-5753
- s390/speculation: Support 'mitigations=' cmdline option

  * CVE-2017-5715 // CVE-2017-5753 // CVE-2017-5754 // CVE-2018-3639
- powerpc/speculation: Support 'mitigations=' cmdline option

  * CVE-2017-5715 // CVE-2017-5754 // CVE-2018-3620 // CVE-2018-3639 //
CVE-2018-3646
- cpu/speculation: Add 'mitigations=' cmdline option
- x86/speculation: Support 'mitigations=' cmdline option

  * Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log

linux (4.15.0-49.53) bionic; urgency=medium

  * linux: 4.15.0-49.53 -proposed tracker (LP: #1826358)

  * Backport support for software count cache flush Spectre v2 mitigation. (CVE)
(required for POWER9 DD2.3) (LP: #1822870)
- powerpc/64s: Add support for ori barrier_nospec patching
- powerpc/64s: Patch barrier_nospec in modules
- powerpc/64s: Enable barrier_nospec based on firmware settings
- powerpc: Use barrier_nospec in copy_from_user()
- powerpc/64: Use barrier_nospec in syscall entry
- powerpc/64s: Enhance the information in cpu_show_spectre_v1()
- powerpc/64: Disable the speculation barrier from the command line
- powerpc/64: Make stf barrier PPC_BOOK3S_64 specific.
- powerpc/64: Add CONFIG_PPC_BARRIER_NOSPEC
- powerpc/64: Call setup_barrier_nospec() from setup_arch()
- powerpc/64: Make meltdown reporting Book3S 64 specific
- powerpc/lib/code-patching: refactor patch_instruction()
- powerpc/lib/feature-fixups: use raw_patch_instruction()
- powerpc/asm: Add a patch_site macro & helpers for patching instructions
- powerpc/64s: Add new security feature flags for count cache flush
- powerpc/64s: Add support for software count cache flush
- powerpc/pseries: Query hypervisor for count cache flush settings
- powerpc/powernv: Query firmware for count cache flush settings
- powerpc/fsl: Add nospectre_v2 command line argument
- KVM: PPC: Book3S: Add count cache flush parameters to 
kvmppc_get_cpu_char()
- [Config] Add CONFIG_PPC_BARRIER_NOSPEC

  * Packaging resync (LP: #1786013)
- [Packaging] resync git-ubuntu-log

  * autopkgtests run too often, too much and don't skip enough (LP: #1823056)
- [Debian] Set +x on rebuild testcase.
- [Debian] Skip rebuild test, for regression-suite deps.
- [Debian] Make ubuntu-regression-suite skippable on unbootable kernels.
- [Debian] make rebuild use skippable error codes when skipping.
- [Debian] Only run regression-suite, if requested to.

  * bionic: fork out linux-snapdragon into its own topic kernel (LP: #1820868)
- [Packaging] remove arm64 snapdragon from getabis
- [Config] config changes for snapdragon split
- packaging: arm64: disable building the snapdragon flavour
- [Packaging] arm64: Drop snapdragon from kernel-versions

  * CVE-2017-5753
- KVM: arm/arm64: vgic: fix possible spectre-v1 in vgic_get_irq()
- media: dvb_ca_en50221: prevent using slot_info for Spectre attacs
- sysvipc/sem: mitigate semnum index against spectre v1
- libahci: Fix possible Spectre-v1 pmp indexing in ahci_led_store()
- s390/keyboard: sanitize array index in do_kdsk_ioctl
- arm64: fix possible spectre-v1 write in ptrace_hbp_set_event()
- KVM: arm/arm64: vgic: Fix possible spectre-v1 write in 
vgic_mmio_write_apr()
- pktcdvd: Fix possible Spectre-v1 for 

[Bug 1823972] Re: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

2019-04-29 Thread Jakob Unterwurzacher
$ apt-cache policy linux-generic-hwe-16.04
linux-generic-hwe-16.04:
  Installed: 4.15.0.49.70
  Candidate: 4.15.0.49.70
  Version table:
 *** 4.15.0.49.70 500
500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 4.15.0.48.69 500
500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages

$ uname -a
Linux osboxes 4.15.0-49-generic #52~16.04.1-Ubuntu SMP Thu Apr 25 18:54:26 UTC 
2019 x86_64 x86_64 x86_64 GNU/Linux


Issue is fixed.

** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823972

Title:
  bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823972/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1823972] Re: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

2019-04-29 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823972

Title:
  bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823972/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1823972] Re: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

2019-04-24 Thread Kirill Smelkov
@arighi, @kmously, thanks for pulling all fuse patches to bionic/master-
next. Am I right in my understanding that the patches will also
propagate to xenial/hwe eventually?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823972

Title:
  bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823972/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1823972] Re: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

2019-04-23 Thread Khaled El Mously
** Changed in: linux (Ubuntu Bionic)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823972

Title:
  bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823972/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1823972] Re: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

2019-04-12 Thread Kirill Smelkov
@arighi, thanks. Let me know if you need more testing and/or help. Good
luck with the review.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823972

Title:
  bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823972/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1823972] Re: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

2019-04-12 Thread Andrea Righi
All fixes applied here:

 git://git.launchpad.net/~arighi/+git/bionic-linux fuse-fixes

And also sent an SRU pull request. Let's see if they get merged.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823972

Title:
  bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823972/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1823972] Re: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

2019-04-11 Thread Po-Hsu Lin
** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823972

Title:
  bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823972/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1823972] Re: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

2019-04-11 Thread Andrea Righi
@navytux yes, a few of them require minimal changes, but most of them
can be applied cleanly to 4.15.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823972

Title:
  bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823972/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1823972] Re: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

2019-04-11 Thread Kirill Smelkov
Thanks. If I understood correctly, the patches should be more or less
directly applicable to 4.15.y

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823972

Title:
  bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823972/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1823972] Re: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

2019-04-11 Thread Andrea Righi
I'll take a look at the other patches, I think they can be easily
applied to 4.15 if they don't require too much backporting work.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823972

Title:
  bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823972/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1823972] Re: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

2019-04-11 Thread Kirill Smelkov
Andrea, thanks.

What about other fs/fuse/ patches marked as @stable? We have more
problems reported on 4.15.x Ubuntu kernel (see e.g.
https://github.com/hanwen/go-fuse/issues/287) and that is unfortunate
when the fix/patch is known, marked as needed to be applied to stable
kernel, but Ubuntu is not picking those patches up, just because
upstream 4.15 kernel is not LTS release and stopped being updated long
ago, unlike e.g. upstream 4.4 and 4.14 stable releases which are updated
to this day and have all those stable patches I'm talking about.

** Bug watch added: github.com/hanwen/go-fuse/issues #287
   https://github.com/hanwen/go-fuse/issues/287

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823972

Title:
  bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823972/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1823972] Re: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

2019-04-11 Thread Andrea Righi
Sent an SRU fix to include 63576c13bd in Bionic.

** Description changed:

+ SRU Justification:
+ 
+ [Impact]
+ 
+  * Enabling parallel dirops in fuse (FUSE_PARALLEL_DIROPS) may cause a
+ race condition that leave fuse inode's mutex held, triggering a deadlock
+ 
+  * The problem is that the lock and unlock paths are relying on
+ get_fuse_conn(inode)->parallel_dirops to decide if the mutex needs to be
+ acquired/released, but its value might be set in the lock path and unset
+ in the unlock path (leaving the mutex held)
+ 
+ [Test Case]
+ 
+  * A test case that triggers the bug almost immediately can be found
+ here https://github.com/hanwen/go-fuse/pull/288
+ 
+ [Fix]
+ 
+  * Instead of relying on get_fuse_conn(inode)->parallel_dirops both in
+ fuse_lock_inode() and fuse_unlock_inode(), only check this flag in the
+ locking path and pass a variable to fuse_unlock_inode() to determine if
+ the mutex was acquired or not
+ 
+ [Regression Potential]
+ 
+  * Fix has been tested on the affected platform. It is an upstream fix
+ that seems to affect only 4.7+ kernels, more exactly in our case only
+ Bionic kernels (and derived) are affected. Cosmic+ already include this
+ fix. So regression potential is minimal.
+ 
+ [Original bug report]
+ 
  Hello up there,
  
  We were reported about a deadlock in the kernel while using a FUSE-based 
filesystem on Ubuntu.
  The kernel in question is Ubuntu-hwe-4.15.0-47.50~16.04.1 from Xenial/HWE. We 
tracked this bug to the fact that 4.15.x kernel in Ubuntu does not include the 
following patch, in despite the patch being marked as needed for v4.7+ stable 
kernels:
  
  https://git.kernel.org/linus/63576c13bd
  
  Please see the following go-fuse issue for full details:
  
  https://github.com/hanwen/go-fuse/issues/281#issuecomment-480008562
  
  The bug is potentially applicable to libfuse users too since libfuse by
  default enables parallel dirops whenever kernel claims support for it,
  which libfuse maintained confirmed:
  
  https://github.com/hanwen/go-fuse/issues/281#issuecomment-480013202
  https://github.com/hanwen/go-fuse/issues/281#issuecomment-480510381
  
  We tested that cherry-picking 63576c13bd into 4.15.x series makes the
  problem go away:
  
  https://github.com/hanwen/go-fuse/issues/281#issuecomment-480499969
  
  So please include https://git.kernel.org/linus/63576c13bd into Ubuntu
  4.15.x kernel series which are bionic/master and xenial/hwe, and which
  currently don't have this patch.
  
  
  
- 
- Here is a full list of FUSE patches marked to be needed in stable kernels 
starting from v4.15:
+ Here is a full list of FUSE patches marked to be needed in stable
+ kernels starting from v4.15:
  
  kirr@deco:~/src/linux/linux$ git log --oneline v4.15..v5.1-rc3 
--grep="stable@" -- fs/fuse/
  a2ebba824106 fuse: decrement NR_WRITEBACK_TEMP on the right page
  9509941e9c53 fuse: call pipe_buf_release() under pipe lock
  8a3177db59cd cuse: fix ioctl
  97e1532ef81a fuse: handle zero sized retrieve correctly
  2e64ff154ce6 fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns 
ENOSYS
  ebacb8127359 fuse: fix use-after-free in fuse_direct_IO()
  2d84a2d19b61 fuse: fix possibly missed wake-up after abort
  7fabaf303458 fuse: fix leaked notify reply
  908a572b80f6 fuse: fix blocked_waitq wakeup
  4c316f2f3ff3 fuse: set FR_SENT while locked
  d2d2d4fb1f54 fuse: Fix use-after-free in fuse_dev_do_write()
  bc78abbd55dd fuse: Fix use-after-free in fuse_dev_do_read()
  a2477b0e67c5 fuse: Don't access pipe->buffers without pipe_lock()
  63576c13bd17 fuse: fix initial parallel dirops
  e8f3bd773d22 fuse: Fix oops at process_init_reply()
  b8f95e5d13f5 fuse: umount should wait for all requests
  45ff350bbd9d fuse: fix unlocked access to processing queue
  87114373ea50 fuse: fix double request_end()
  543b8f8662fe (tag: fuse-update-4.18) fuse: don't keep dead fuse_conn at 
fuse_fill_super().
  6becdb601bae fuse: fix control dir setup and teardown
  8a301eb16d99 fuse: fix congested state leak on aborted connections
  df0e91d48827 fuse: atomic_o_trunc should truncate pagecache
  
  Among those only 8a3177db59cd and 2d84a2d19b61 should not be applied to
  4.15.x becuase they cure a problem introduced in a later kernel (please
  see got log without --oneline for stable@ details)
  
  However both bionic and xenial/hwe has much less fuse patches applied:
  
- 
  kirr@deco:~/src/linux/linux$ git log --oneline v4.15..bionic/master  -- 
fs/fuse/
  e992e3521885 fuse: fix control dir setup and teardown
  f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super().
  840c77082f93 fuse: atomic_o_trunc should truncate pagecache
  c0e31b214498 fuse: fix congested state leak on aborted connections
  45f23c59120f UBUNTU: SAUCE: (namespace) fuse: Allow user namespace mounts
  1223588451c6 UBUNTU: SAUCE: (namespace) fuse: Restrict allow_other to the 
superblock's namespace or a descendant
  b4d1889491a0 UBUNTU: SAUCE: (namespace) fuse: Support fuse filesystems 

[Bug 1823972] Re: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

2019-04-09 Thread Kirill Smelkov
** Tags added: bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823972

Title:
  bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823972/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1823972] Re: bionic, xenial/hwe: misses "fuse: fix initial parallel dirops" patch

2019-04-09 Thread Kirill Smelkov
apport information

** Tags added: apport-collected

** Description changed:

  Hello up there,
  
  We were reported about a deadlock in the kernel while using a FUSE-based 
filesystem on Ubuntu.
  The kernel in question is Ubuntu-hwe-4.15.0-47.50~16.04.1 from Xenial/HWE. We 
tracked this bug to the fact that 4.15.x kernel in Ubuntu does not include the 
following patch, in despite the patch being marked as needed for v4.7+ stable 
kernels:
  
  https://git.kernel.org/linus/63576c13bd
  
  Please see the following go-fuse issue for full details:
  
  https://github.com/hanwen/go-fuse/issues/281#issuecomment-480008562
  
  The bug is potentially applicable to libfuse users too since libfuse by
  default enables parallel dirops whenever kernel claims support for it,
  which libfuse maintained confirmed:
  
  https://github.com/hanwen/go-fuse/issues/281#issuecomment-480013202
  https://github.com/hanwen/go-fuse/issues/281#issuecomment-480510381
  
  We tested that cherry-picking 63576c13bd into 4.15.x series makes the
  problem go away:
  
  https://github.com/hanwen/go-fuse/issues/281#issuecomment-480499969
  
  So please include https://git.kernel.org/linus/63576c13bd into Ubuntu
  4.15.x kernel series which are bionic/master and xenial/hwe, and which
  currently don't have this patch.
  
  
  
  
  Here is a full list of FUSE patches marked to be needed in stable kernels 
starting from v4.15:
  
  kirr@deco:~/src/linux/linux$ git log --oneline v4.15..v5.1-rc3 
--grep="stable@" -- fs/fuse/
  a2ebba824106 fuse: decrement NR_WRITEBACK_TEMP on the right page
  9509941e9c53 fuse: call pipe_buf_release() under pipe lock
  8a3177db59cd cuse: fix ioctl
  97e1532ef81a fuse: handle zero sized retrieve correctly
  2e64ff154ce6 fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns 
ENOSYS
  ebacb8127359 fuse: fix use-after-free in fuse_direct_IO()
  2d84a2d19b61 fuse: fix possibly missed wake-up after abort
  7fabaf303458 fuse: fix leaked notify reply
  908a572b80f6 fuse: fix blocked_waitq wakeup
  4c316f2f3ff3 fuse: set FR_SENT while locked
  d2d2d4fb1f54 fuse: Fix use-after-free in fuse_dev_do_write()
  bc78abbd55dd fuse: Fix use-after-free in fuse_dev_do_read()
  a2477b0e67c5 fuse: Don't access pipe->buffers without pipe_lock()
  63576c13bd17 fuse: fix initial parallel dirops
  e8f3bd773d22 fuse: Fix oops at process_init_reply()
  b8f95e5d13f5 fuse: umount should wait for all requests
  45ff350bbd9d fuse: fix unlocked access to processing queue
  87114373ea50 fuse: fix double request_end()
  543b8f8662fe (tag: fuse-update-4.18) fuse: don't keep dead fuse_conn at 
fuse_fill_super().
  6becdb601bae fuse: fix control dir setup and teardown
  8a301eb16d99 fuse: fix congested state leak on aborted connections
  df0e91d48827 fuse: atomic_o_trunc should truncate pagecache
  
  Among those only 8a3177db59cd and 2d84a2d19b61 should not be applied to
  4.15.x becuase they cure a problem introduced in a later kernel (please
  see got log without --oneline for stable@ details)
  
  However both bionic and xenial/hwe has much less fuse patches applied:
  
  
  kirr@deco:~/src/linux/linux$ git log --oneline v4.15..bionic/master  -- 
fs/fuse/
  e992e3521885 fuse: fix control dir setup and teardown
  f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super().
  840c77082f93 fuse: atomic_o_trunc should truncate pagecache
  c0e31b214498 fuse: fix congested state leak on aborted connections
  45f23c59120f UBUNTU: SAUCE: (namespace) fuse: Allow user namespace mounts
  1223588451c6 UBUNTU: SAUCE: (namespace) fuse: Restrict allow_other to the 
superblock's namespace or a descendant
  b4d1889491a0 UBUNTU: SAUCE: (namespace) fuse: Support fuse filesystems 
outside of init_user_ns
  
  
  kirr@deco:~/src/linux/linux$ git log --oneline v4.15..xenial/hwe  -- fs/fuse/
  e992e3521885 fuse: fix control dir setup and teardown
  f3a3e0537dcd fuse: don't keep dead fuse_conn at fuse_fill_super().
  840c77082f93 fuse: atomic_o_trunc should truncate pagecache
  c0e31b214498 fuse: fix congested state leak on aborted connections
  45f23c59120f UBUNTU: SAUCE: (namespace) fuse: Allow user namespace mounts
  1223588451c6 UBUNTU: SAUCE: (namespace) fuse: Restrict allow_other to the 
superblock's namespace or a descendant
  b4d1889491a0 UBUNTU: SAUCE: (namespace) fuse: Support fuse filesystems 
outside of init_user_ns
  
  
  which suggests that other FUSE fixes should be cherry-picked too.
  
  Please consider cherry-picking those additional patches too. They are all in 
upstream kernel 
  stable series, e.g. stable/linux-4.14.y has them:
  
  kirr@deco:~/src/linux/linux$ git log --oneline v4.14..stable/linux-4.14.y -- 
fs/fuse/
  266a69895b89 fuse: handle zero sized retrieve correctly
  b928e93d864c fuse: decrement NR_WRITEBACK_TEMP on the right page
  65f222bb370e fuse: call pipe_buf_release() under pipe lock
  c1149b873482 fuse: continue to send FUSE_RELEASEDIR when FUSE_OPEN returns 
ENOSYS
  6ceec07cc84a fuse: fix leaked