** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793451
Title:
mlock203 test in ubuntu_ltp_syscalls failed with Xenial kernel
This bug was fixed in the package linux - 4.4.0-140.166
---
linux (4.4.0-140.166) xenial; urgency=medium
* linux: 4.4.0-140.166 -proposed tracker (LP: #1802776)
* Bypass of mount visibility through userns + mount propagation (LP: #1789161)
- mount: Retest MNT_LOCKED in
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: linux (Ubuntu)
Assignee: Po-Hsu Lin (cypressyew) => (unassigned)
** Changed in: ubuntu-kernel-tests
Status: In Progress => Fix Released
--
You received this bug notification
Passed with Xenial SRU
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793451
Title:
mlock203 test in
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-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
** Changed in: linux (Ubuntu Xenial)
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/1793451
Title:
mlock203 test in ubuntu_ltp_syscalls failed with Xenial kernel
I deleted the linux-aws task(s) because this will get fixed in the
master kernel and then automatically end up in all derivatives. No need
to track it for every derivative.
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux-aws (Ubuntu
** Description changed:
== Justification ==
When one vma was with flag VM_LOCKED|VM_LOCKONFAULT (by invoking
mlock2(,MLOCK_ONFAULT)), it can again be populated with mlock() with
VM_LOCKED flag only.
There is a hole in mlock_fixup() which increase mm->locked_vm twice even
the two
** Description changed:
- 15:11:31 DEBUG| [stdout] <<>>
- 15:11:31 DEBUG| [stdout] tag=mlock203 stime=1537369891
- 15:11:31 DEBUG| [stdout] cmdline="mlock203"
- 15:11:31 DEBUG| [stdout] contacts=""
- 15:11:31 DEBUG| [stdout] analysis=exit
- 15:11:31 DEBUG| [stdout] <<>>
- 15:11:31 DEBUG| [stdout]
** Summary changed:
- mlock203 test in ubuntu_ltp_syscalls failed with X-AWS
+ mlock203 test in ubuntu_ltp_syscalls failed with Xenial kernel
** Changed in: ubuntu-kernel-tests
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: ubuntu-kernel-tests
Status: New => In
10 matches
Mail list logo
