Duplicating my post to the fuse developer mailing list here:
Hi all,
the kernel crash can be triggered if async direct IO is used which comes
with Fuse 3.0_pre0 (i.e. current head). My workload was to install
CentOS7 on a newly created qcow2 disk. The kernel (Fedora 21;
4.1.8-100.fc21.x86_64) cra
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Tags added: kernel-da-key wily
** Also affects: linux (Ubuntu Wily)
Importance: High
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-
stable.git/diff/fs/fuse/file.c?id=refs/tags/v4.1&id2=refs/tags/v4.0 is
the diff between the version that works and the one that is broken. The
candidate that broke functionality is likely here:
https://lkml.org/lkml/2015/4/13/871
https://l
We can now confirm that the issue does not happen with 4.0.9. This leads
to the assumption that the problem has either been fixed between 4.0 and
4.0.9, or, and I consider this much more likely, the problem was
introduced between 4.0 and 4.1 on the main branch.
--
You received this bug notificati
** Attachment added: "uname -a log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1505948/+attachment/4494210/+files/uname-a.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1505948
Title:
** Attachment added: "/proc/version output"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1505948/+attachment/4494211/+files/version.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1505948
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1398465 also
appears to be the same issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1505948
Title:
Memory allocation failure crashes kernel
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1505948
Title:
Memo
As already mentioned in my email to the fuse developer mailing list, we
have also tried to create direct i/o traffic on the affected mount
directly but were not able to reproduce the issue. The problem only ever
occurs once Qemu starts to run stuff on top of the FUSE mount. Other
reports of this is
