[Kernel-packages] [Bug 1799237] Re: mprotect fails on ext4 with dax

2019-02-17 Thread Christian Priebe
I have not had a chance to try and reproduce the issue with the example mentioned in this bug report but I have been able to verify that the kernel in bionic-proposed fixes the problem I have reported in the following bug report that has been rightfully marked as a duplicate: https://bugs.launchpa

[Kernel-packages] [Bug 1813179] Re: Bionic (4.15.0-43.46), x86: mprotect(..., PROT_NONE) failure for VM_PFNMAP VMAs (fixed in mainline)

2019-01-25 Thread Christian Priebe
I had previously missed this bug report on the same issue: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799237 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813179 Title: Bio

[Kernel-packages] [Bug 1799237] Re: mprotect fails on ext4 with dax

2019-01-25 Thread Christian Priebe
I missed this report when I submitted my own report yesterday (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813179). In my case there is no workaround, so I am hoping this can be backported. It is a one-line fix. -- You received this bug notification because you are a member of Kernel Pa

[Kernel-packages] [Bug 1813179] Re: Bionic (4.15.0-43.46), x86: mprotect(..., PROT_NONE) failure for VM_PFNMAP VMAs (fixed in mainline)

2019-01-24 Thread Christian Priebe
I don't believe log files are required in this case. Changing bug status to 'Confirmed'. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.la

[Kernel-packages] [Bug 1813179] [NEW] Bionic (4.15.0-43.46), x86: mprotect(..., PROT_NONE) failure for VM_PFNMAP VMAs (fixed in mainline)

2019-01-24 Thread Christian Priebe
Public bug reported: Version: Distributor ID: Ubuntu Description:Ubuntu 18.04.1 LTS Release:18.04 Codename: bionic Ubuntu 4.15.0-43.46-generic 4.15.18 This is a bug that has been fixed in mainline. When calling 'mprotect(..., PROT_NONE)' on a virtual memory area with VM_PFNMAP