[Kernel-packages] [Bug 1983640] Re: refactoring of overlayfs fix to properly support shiftfs
Ubuntu 22.10 (Kinetic Kudu) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: linux-hwe-5.17 (Ubuntu Kinetic)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1983640
Title:
refactoring of overlayfs fix to properly support shiftfs
Status in linux package in Ubuntu:
Fix Released
Status in linux-hwe-5.17 package in Ubuntu:
Confirmed
Status in linux source package in Jammy:
Fix Released
Status in linux-hwe-5.17 source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
Fix Released
Status in linux-hwe-5.17 source package in Kinetic:
Won't Fix
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch is required to use overlayfs on top of shiftfs and without
this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
However, we made this patch dependent on AUFS, starting with Jammy
we're not enabling AUFS anymore, so this fix becomes a no-op.
So we need to re-introduce this fix with a bit of refactoring to not
depend on AUFS.
[Test case]
The following script can be used to trigger the issue:
#!/bin/bash
cat > test.py << EOF
import sys
f = open("/proc/self/maps")
for l in f.readlines():
if "python" not in l:
continue
print(l)
s = l.split()
start, end = s[0].split("-")
fname = s[-1]
print(start, end, fname)
break
else:
sys.exit(1)
test_file1 = open(fname)
test_file2 = open("/proc/self/map_files/%s-%s" % (start, end))
fdinfo1 = open("/proc/self/fdinfo/%d" % test_file1.fileno()).read()
fdinfo2 = open("/proc/self/fdinfo/%d" % test_file2.fileno()).read()
if fdinfo1 != fdinfo2:
print("FAIL")
print(test_file1)
print(fdinfo1)
print(test_file2)
print(fdinfo2)
sys.exit(1)
print("PASS")
EOF
sudo docker run -it --privileged --rm -v `pwd`:/mnt python python
/mnt/test.py
[Fix]
Import the right pieces from AUFS to properly support the fix and get
rid of the AUFS dependency across all our kernels and re-apply the
overlayfs fix without the AUFS dependency.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs, especially when containers are used.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983640/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983640] Re: refactoring of overlayfs fix to properly support shiftfs
This bug is awaiting verification that the linux-mtk/5.15.0-1030.34
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-jammy-linux-mtk' to 'verification-done-jammy-
linux-mtk'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'.
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: kernel-spammed-jammy-linux-mtk-v2
verification-needed-jammy-linux-mtk
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1983640
Title:
refactoring of overlayfs fix to properly support shiftfs
Status in linux package in Ubuntu:
Fix Released
Status in linux-hwe-5.17 package in Ubuntu:
Confirmed
Status in linux source package in Jammy:
Fix Released
Status in linux-hwe-5.17 source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
Fix Released
Status in linux-hwe-5.17 source package in Kinetic:
Confirmed
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch is required to use overlayfs on top of shiftfs and without
this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
However, we made this patch dependent on AUFS, starting with Jammy
we're not enabling AUFS anymore, so this fix becomes a no-op.
So we need to re-introduce this fix with a bit of refactoring to not
depend on AUFS.
[Test case]
The following script can be used to trigger the issue:
#!/bin/bash
cat > test.py << EOF
import sys
f = open("/proc/self/maps")
for l in f.readlines():
if "python" not in l:
continue
print(l)
s = l.split()
start, end = s[0].split("-")
fname = s[-1]
print(start, end, fname)
break
else:
sys.exit(1)
test_file1 = open(fname)
test_file2 = open("/proc/self/map_files/%s-%s" % (start, end))
fdinfo1 = open("/proc/self/fdinfo/%d" % test_file1.fileno()).read()
fdinfo2 = open("/proc/self/fdinfo/%d" % test_file2.fileno()).read()
if fdinfo1 != fdinfo2:
print("FAIL")
print(test_file1)
print(fdinfo1)
print(test_file2)
print(fdinfo2)
sys.exit(1)
print("PASS")
EOF
sudo docker run -it --privileged --rm -v `pwd`:/mnt python python
/mnt/test.py
[Fix]
Import the right pieces from AUFS to properly support the fix and get
rid of the AUFS dependency across all our kernels and re-apply the
overlayfs fix without the AUFS dependency.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs, especially when containers are used.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983640/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983640] Re: refactoring of overlayfs fix to properly support shiftfs
This bug is awaiting verification that the linux-
bluefield/5.15.0-1010.12 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-jammy' to 'verification-
done-jammy'. If the problem still exists, change the tag 'verification-
needed-jammy' to 'verification-failed-jammy'.
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: kernel-spammed-jammy-linux-bluefield verification-needed-jammy
--
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/1983640
Title:
refactoring of overlayfs fix to properly support shiftfs
Status in linux package in Ubuntu:
Fix Released
Status in linux-hwe-5.17 package in Ubuntu:
Confirmed
Status in linux source package in Jammy:
Fix Released
Status in linux-hwe-5.17 source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
Fix Released
Status in linux-hwe-5.17 source package in Kinetic:
Confirmed
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch is required to use overlayfs on top of shiftfs and without
this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
However, we made this patch dependent on AUFS, starting with Jammy
we're not enabling AUFS anymore, so this fix becomes a no-op.
So we need to re-introduce this fix with a bit of refactoring to not
depend on AUFS.
[Test case]
The following script can be used to trigger the issue:
#!/bin/bash
cat > test.py << EOF
import sys
f = open("/proc/self/maps")
for l in f.readlines():
if "python" not in l:
continue
print(l)
s = l.split()
start, end = s[0].split("-")
fname = s[-1]
print(start, end, fname)
break
else:
sys.exit(1)
test_file1 = open(fname)
test_file2 = open("/proc/self/map_files/%s-%s" % (start, end))
fdinfo1 = open("/proc/self/fdinfo/%d" % test_file1.fileno()).read()
fdinfo2 = open("/proc/self/fdinfo/%d" % test_file2.fileno()).read()
if fdinfo1 != fdinfo2:
print("FAIL")
print(test_file1)
print(fdinfo1)
print(test_file2)
print(fdinfo2)
sys.exit(1)
print("PASS")
EOF
sudo docker run -it --privileged --rm -v `pwd`:/mnt python python
/mnt/test.py
[Fix]
Import the right pieces from AUFS to properly support the fix and get
rid of the AUFS dependency across all our kernels and re-apply the
overlayfs fix without the AUFS dependency.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs, especially when containers are used.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983640/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983640] Re: refactoring of overlayfs fix to properly support shiftfs
This bug is awaiting verification that the linux-
bluefield/5.15.0-1009.11 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-jammy' to 'verification-
done-jammy'. If the problem still exists, change the tag 'verification-
needed-jammy' to 'verification-failed-jammy'.
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!
--
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/1983640
Title:
refactoring of overlayfs fix to properly support shiftfs
Status in linux package in Ubuntu:
Fix Released
Status in linux-hwe-5.17 package in Ubuntu:
Confirmed
Status in linux source package in Jammy:
Fix Released
Status in linux-hwe-5.17 source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
Fix Released
Status in linux-hwe-5.17 source package in Kinetic:
Confirmed
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch is required to use overlayfs on top of shiftfs and without
this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
However, we made this patch dependent on AUFS, starting with Jammy
we're not enabling AUFS anymore, so this fix becomes a no-op.
So we need to re-introduce this fix with a bit of refactoring to not
depend on AUFS.
[Test case]
The following script can be used to trigger the issue:
#!/bin/bash
cat > test.py << EOF
import sys
f = open("/proc/self/maps")
for l in f.readlines():
if "python" not in l:
continue
print(l)
s = l.split()
start, end = s[0].split("-")
fname = s[-1]
print(start, end, fname)
break
else:
sys.exit(1)
test_file1 = open(fname)
test_file2 = open("/proc/self/map_files/%s-%s" % (start, end))
fdinfo1 = open("/proc/self/fdinfo/%d" % test_file1.fileno()).read()
fdinfo2 = open("/proc/self/fdinfo/%d" % test_file2.fileno()).read()
if fdinfo1 != fdinfo2:
print("FAIL")
print(test_file1)
print(fdinfo1)
print(test_file2)
print(fdinfo2)
sys.exit(1)
print("PASS")
EOF
sudo docker run -it --privileged --rm -v `pwd`:/mnt python python
/mnt/test.py
[Fix]
Import the right pieces from AUFS to properly support the fix and get
rid of the AUFS dependency across all our kernels and re-apply the
overlayfs fix without the AUFS dependency.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs, especially when containers are used.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983640/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983640] Re: refactoring of overlayfs fix to properly support shiftfs
Kernel 5.19 is also affected
** Changed in: linux-hwe-5.17 (Ubuntu Kinetic)
Status: Invalid => Confirmed
--
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/1983640
Title:
refactoring of overlayfs fix to properly support shiftfs
Status in linux package in Ubuntu:
Fix Released
Status in linux-hwe-5.17 package in Ubuntu:
Confirmed
Status in linux source package in Jammy:
Fix Released
Status in linux-hwe-5.17 source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
Fix Released
Status in linux-hwe-5.17 source package in Kinetic:
Confirmed
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch is required to use overlayfs on top of shiftfs and without
this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
However, we made this patch dependent on AUFS, starting with Jammy
we're not enabling AUFS anymore, so this fix becomes a no-op.
So we need to re-introduce this fix with a bit of refactoring to not
depend on AUFS.
[Test case]
The following script can be used to trigger the issue:
#!/bin/bash
cat > test.py << EOF
import sys
f = open("/proc/self/maps")
for l in f.readlines():
if "python" not in l:
continue
print(l)
s = l.split()
start, end = s[0].split("-")
fname = s[-1]
print(start, end, fname)
break
else:
sys.exit(1)
test_file1 = open(fname)
test_file2 = open("/proc/self/map_files/%s-%s" % (start, end))
fdinfo1 = open("/proc/self/fdinfo/%d" % test_file1.fileno()).read()
fdinfo2 = open("/proc/self/fdinfo/%d" % test_file2.fileno()).read()
if fdinfo1 != fdinfo2:
print("FAIL")
print(test_file1)
print(fdinfo1)
print(test_file2)
print(fdinfo2)
sys.exit(1)
print("PASS")
EOF
sudo docker run -it --privileged --rm -v `pwd`:/mnt python python
/mnt/test.py
[Fix]
Import the right pieces from AUFS to properly support the fix and get
rid of the AUFS dependency across all our kernels and re-apply the
overlayfs fix without the AUFS dependency.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs, especially when containers are used.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983640/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983640] Re: refactoring of overlayfs fix to properly support shiftfs
This bug is awaiting verification that the linux-ibm/5.15.0-1015.17
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-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.
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!
--
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/1983640
Title:
refactoring of overlayfs fix to properly support shiftfs
Status in linux package in Ubuntu:
Fix Released
Status in linux-hwe-5.17 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux-hwe-5.17 source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
Fix Released
Status in linux-hwe-5.17 source package in Kinetic:
Invalid
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch is required to use overlayfs on top of shiftfs and without
this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
However, we made this patch dependent on AUFS, starting with Jammy
we're not enabling AUFS anymore, so this fix becomes a no-op.
So we need to re-introduce this fix with a bit of refactoring to not
depend on AUFS.
[Test case]
The following script can be used to trigger the issue:
#!/bin/bash
cat > test.py << EOF
import sys
f = open("/proc/self/maps")
for l in f.readlines():
if "python" not in l:
continue
print(l)
s = l.split()
start, end = s[0].split("-")
fname = s[-1]
print(start, end, fname)
break
else:
sys.exit(1)
test_file1 = open(fname)
test_file2 = open("/proc/self/map_files/%s-%s" % (start, end))
fdinfo1 = open("/proc/self/fdinfo/%d" % test_file1.fileno()).read()
fdinfo2 = open("/proc/self/fdinfo/%d" % test_file2.fileno()).read()
if fdinfo1 != fdinfo2:
print("FAIL")
print(test_file1)
print(fdinfo1)
print(test_file2)
print(fdinfo2)
sys.exit(1)
print("PASS")
EOF
sudo docker run -it --privileged --rm -v `pwd`:/mnt python python
/mnt/test.py
[Fix]
Import the right pieces from AUFS to properly support the fix and get
rid of the AUFS dependency across all our kernels and re-apply the
overlayfs fix without the AUFS dependency.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs, especially when containers are used.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983640/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983640] Re: refactoring of overlayfs fix to properly support shiftfs
This bug is awaiting verification that the linux-
bluefield/5.15.0-1008.10 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-jammy' to 'verification-
done-jammy'. If the problem still exists, change the tag 'verification-
needed-jammy' to 'verification-failed-jammy'.
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!
--
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/1983640
Title:
refactoring of overlayfs fix to properly support shiftfs
Status in linux package in Ubuntu:
Fix Released
Status in linux-hwe-5.17 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux-hwe-5.17 source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
Fix Released
Status in linux-hwe-5.17 source package in Kinetic:
Invalid
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch is required to use overlayfs on top of shiftfs and without
this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
However, we made this patch dependent on AUFS, starting with Jammy
we're not enabling AUFS anymore, so this fix becomes a no-op.
So we need to re-introduce this fix with a bit of refactoring to not
depend on AUFS.
[Test case]
The following script can be used to trigger the issue:
#!/bin/bash
cat > test.py << EOF
import sys
f = open("/proc/self/maps")
for l in f.readlines():
if "python" not in l:
continue
print(l)
s = l.split()
start, end = s[0].split("-")
fname = s[-1]
print(start, end, fname)
break
else:
sys.exit(1)
test_file1 = open(fname)
test_file2 = open("/proc/self/map_files/%s-%s" % (start, end))
fdinfo1 = open("/proc/self/fdinfo/%d" % test_file1.fileno()).read()
fdinfo2 = open("/proc/self/fdinfo/%d" % test_file2.fileno()).read()
if fdinfo1 != fdinfo2:
print("FAIL")
print(test_file1)
print(fdinfo1)
print(test_file2)
print(fdinfo2)
sys.exit(1)
print("PASS")
EOF
sudo docker run -it --privileged --rm -v `pwd`:/mnt python python
/mnt/test.py
[Fix]
Import the right pieces from AUFS to properly support the fix and get
rid of the AUFS dependency across all our kernels and re-apply the
overlayfs fix without the AUFS dependency.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs, especially when containers are used.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983640/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983640] Re: refactoring of overlayfs fix to properly support shiftfs
This bug was fixed in the package linux - 5.19.0-18.18 --- linux (5.19.0-18.18) kinetic; urgency=medium * kinetic/linux: 5.19.0-18.18 -proposed tracker (LP: #1990366) * 5.19.0-17.17: kernel NULL pointer dereference, address: 0084 (LP: #1990236) - Revert "UBUNTU: SAUCE: apparmor: Fix regression in stacking due to label flags" - Revert "UBUNTU: [Config] disable SECURITY_APPARMOR_RESTRICT_USERNS" - Revert "UBUNTU: SAUCE: Revert "hwrng: virtio - add an internal buffer"" - Revert "UBUNTU: SAUCE: Revert "hwrng: virtio - don't wait on cleanup"" - Revert "UBUNTU: SAUCE: Revert "hwrng: virtio - don't waste entropy"" - Revert "UBUNTU: SAUCE: Revert "hwrng: virtio - always add a pending request"" - Revert "UBUNTU: SAUCE: Revert "hwrng: virtio - unregister device before reset"" - Revert "UBUNTU: SAUCE: Revert "virtio-rng: make device ready before making request"" - Revert "UBUNTU: [Config] update configs after apply new apparmor patch set" - Revert "UBUNTU: SAUCE: apparmor: add user namespace creation mediation" - Revert "UBUNTU: SAUCE: selinux: Implement userns_create hook" - Revert "UBUNTU: SAUCE: bpf-lsm: Make bpf_lsm_userns_create() sleepable" - Revert "UBUNTU: SAUCE: security, lsm: Introduce security_create_user_ns()" - Revert "UBUNTU: SAUCE: lsm stacking v37: AppArmor: Remove the exclusive flag" - Revert "UBUNTU: SAUCE: lsm stacking v37: LSM: Add /proc attr entry for full LSM context" - Revert "UBUNTU: SAUCE: lsm stacking v37: LSM: Removed scaffolding function lsmcontext_init" - Revert "UBUNTU: SAUCE: lsm stacking v37: netlabel: Use a struct lsmblob in audit data" - Revert "UBUNTU: SAUCE: lsm stacking v37: Audit: Add record for multiple object contexts" - Revert "UBUNTU: SAUCE: lsm stacking v37: audit: multiple subject lsm values for netlabel" - Revert "UBUNTU: SAUCE: lsm stacking v37: Audit: Add record for multiple task security contexts" - Revert "UBUNTU: SAUCE: lsm stacking v37: Audit: Allow multiple records in an audit_buffer" - Revert "UBUNTU: SAUCE: lsm stacking v37: LSM: Add a function to report multiple LSMs" - Revert "UBUNTU: SAUCE: lsm stacking v37: Audit: Create audit_stamp structure" - Revert "UBUNTU: SAUCE: lsm stacking v37: Audit: Keep multiple LSM data in audit_names" - Revert "UBUNTU: SAUCE: lsm stacking v37: LSM: security_secid_to_secctx module selection" - Revert "UBUNTU: SAUCE: lsm stacking v37: binder: Pass LSM identifier for confirmation" - Revert "UBUNTU: SAUCE: lsm stacking v37: NET: Store LSM netlabel data in a lsmblob" - Revert "UBUNTU: SAUCE: lsm stacking v37: LSM: security_secid_to_secctx in netlink netfilter" - Revert "UBUNTU: SAUCE: lsm stacking v37: LSM: Use lsmcontext in security_dentry_init_security" - Revert "UBUNTU: SAUCE: lsm stacking v37: LSM: Use lsmcontext in security_inode_getsecctx" - Revert "UBUNTU: SAUCE: lsm stacking v37: LSM: Use lsmcontext in security_secid_to_secctx" - Revert "UBUNTU: SAUCE: lsm stacking v37: LSM: Ensure the correct LSM context releaser" - Revert "UBUNTU: SAUCE: fixup lsm stacking v37: LSM: Specify which LSM to display" - Revert "UBUNTU: SAUCE: lsm stacking v37: LSM: Specify which LSM to display" - Revert "UBUNTU: SAUCE: lsm stacking v37: LSM: Use lsmblob in security_cred_getsecid" - Revert "UBUNTU: SAUCE: lsm stacking v37: LSM: Use lsmblob in security_inode_getsecid" - Revert "UBUNTU: SAUCE: lsm stacking v37: LSM: Use lsmblob in security_current_getsecid" - Revert "UBUNTU: SAUCE: lsm stacking v37: LSM: Use lsmblob in security_ipc_getsecid" - Revert "UBUNTU: SAUCE: lsm stacking v37: LSM: Use lsmblob in security_secid_to_secctx" - Revert "UBUNTU: SAUCE: lsm stacking v37: LSM: Use lsmblob in security_secctx_to_secid" - Revert "UBUNTU: SAUCE: lsm stacking v37: LSM: Use lsmblob in security_kernel_act_as" - Revert "UBUNTU: SAUCE: lsm stacking v37: LSM: Use lsmblob in security_audit_rule_match" - Revert "UBUNTU: SAUCE: lsm stacking v37: IMA: avoid label collisions with stacked LSMs" - Revert "UBUNTU: SAUCE: lsm stacking v37: LSM: provide lsm name and id slot mappings" - Revert "UBUNTU: SAUCE: lsm stacking v37: LSM: Add the lsmblob data structure." - Revert "UBUNTU: SAUCE: lsm stacking v37: LSM: Infrastructure management of the sock security" - Revert "UBUNTU: SAUCE: lsm stacking v37: integrity: disassociate ima_filter_rule from security_audit_rule" - Revert "UBUNTU: SAUCE: apparmor: LSM stacking: switch from SK_CTX() to aa_sock()" - Revert "UBUNTU: SAUCE: apparmor: Add fine grained mediation of posix mqueues" - Revert "UBUNTU: SAUCE: apparmor: rename aa_sock() to aa_unix_sk()" -
[Kernel-packages] [Bug 1983640] Re: refactoring of overlayfs fix to properly support shiftfs
This bug is awaiting verification that the linux-
gkeop-5.15/5.15.0-1003.5~20.04.2 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-focal' to
'verification-done-focal'. If the problem still exists, change the tag
'verification-needed-focal' to 'verification-failed-focal'.
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!
--
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/1983640
Title:
refactoring of overlayfs fix to properly support shiftfs
Status in linux package in Ubuntu:
Fix Committed
Status in linux-hwe-5.17 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux-hwe-5.17 source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
Fix Committed
Status in linux-hwe-5.17 source package in Kinetic:
Invalid
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch is required to use overlayfs on top of shiftfs and without
this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
However, we made this patch dependent on AUFS, starting with Jammy
we're not enabling AUFS anymore, so this fix becomes a no-op.
So we need to re-introduce this fix with a bit of refactoring to not
depend on AUFS.
[Test case]
The following script can be used to trigger the issue:
#!/bin/bash
cat > test.py << EOF
import sys
f = open("/proc/self/maps")
for l in f.readlines():
if "python" not in l:
continue
print(l)
s = l.split()
start, end = s[0].split("-")
fname = s[-1]
print(start, end, fname)
break
else:
sys.exit(1)
test_file1 = open(fname)
test_file2 = open("/proc/self/map_files/%s-%s" % (start, end))
fdinfo1 = open("/proc/self/fdinfo/%d" % test_file1.fileno()).read()
fdinfo2 = open("/proc/self/fdinfo/%d" % test_file2.fileno()).read()
if fdinfo1 != fdinfo2:
print("FAIL")
print(test_file1)
print(fdinfo1)
print(test_file2)
print(fdinfo2)
sys.exit(1)
print("PASS")
EOF
sudo docker run -it --privileged --rm -v `pwd`:/mnt python python
/mnt/test.py
[Fix]
Import the right pieces from AUFS to properly support the fix and get
rid of the AUFS dependency across all our kernels and re-apply the
overlayfs fix without the AUFS dependency.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs, especially when containers are used.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983640/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983640] Re: refactoring of overlayfs fix to properly support shiftfs
Appears to be a regression reported about this
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990849
=
--
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/1983640
Title:
refactoring of overlayfs fix to properly support shiftfs
Status in linux package in Ubuntu:
Fix Committed
Status in linux-hwe-5.17 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux-hwe-5.17 source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
Fix Committed
Status in linux-hwe-5.17 source package in Kinetic:
Invalid
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch is required to use overlayfs on top of shiftfs and without
this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
However, we made this patch dependent on AUFS, starting with Jammy
we're not enabling AUFS anymore, so this fix becomes a no-op.
So we need to re-introduce this fix with a bit of refactoring to not
depend on AUFS.
[Test case]
The following script can be used to trigger the issue:
#!/bin/bash
cat > test.py << EOF
import sys
f = open("/proc/self/maps")
for l in f.readlines():
if "python" not in l:
continue
print(l)
s = l.split()
start, end = s[0].split("-")
fname = s[-1]
print(start, end, fname)
break
else:
sys.exit(1)
test_file1 = open(fname)
test_file2 = open("/proc/self/map_files/%s-%s" % (start, end))
fdinfo1 = open("/proc/self/fdinfo/%d" % test_file1.fileno()).read()
fdinfo2 = open("/proc/self/fdinfo/%d" % test_file2.fileno()).read()
if fdinfo1 != fdinfo2:
print("FAIL")
print(test_file1)
print(fdinfo1)
print(test_file2)
print(fdinfo2)
sys.exit(1)
print("PASS")
EOF
sudo docker run -it --privileged --rm -v `pwd`:/mnt python python
/mnt/test.py
[Fix]
Import the right pieces from AUFS to properly support the fix and get
rid of the AUFS dependency across all our kernels and re-apply the
overlayfs fix without the AUFS dependency.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs, especially when containers are used.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983640/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983640] Re: refactoring of overlayfs fix to properly support shiftfs
This bug is awaiting verification that the linux-nvidia/5.15.0-1007.7
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-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.
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!
--
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/1983640
Title:
refactoring of overlayfs fix to properly support shiftfs
Status in linux package in Ubuntu:
Fix Committed
Status in linux-hwe-5.17 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux-hwe-5.17 source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
Fix Committed
Status in linux-hwe-5.17 source package in Kinetic:
Invalid
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch is required to use overlayfs on top of shiftfs and without
this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
However, we made this patch dependent on AUFS, starting with Jammy
we're not enabling AUFS anymore, so this fix becomes a no-op.
So we need to re-introduce this fix with a bit of refactoring to not
depend on AUFS.
[Test case]
The following script can be used to trigger the issue:
#!/bin/bash
cat > test.py << EOF
import sys
f = open("/proc/self/maps")
for l in f.readlines():
if "python" not in l:
continue
print(l)
s = l.split()
start, end = s[0].split("-")
fname = s[-1]
print(start, end, fname)
break
else:
sys.exit(1)
test_file1 = open(fname)
test_file2 = open("/proc/self/map_files/%s-%s" % (start, end))
fdinfo1 = open("/proc/self/fdinfo/%d" % test_file1.fileno()).read()
fdinfo2 = open("/proc/self/fdinfo/%d" % test_file2.fileno()).read()
if fdinfo1 != fdinfo2:
print("FAIL")
print(test_file1)
print(fdinfo1)
print(test_file2)
print(fdinfo2)
sys.exit(1)
print("PASS")
EOF
sudo docker run -it --privileged --rm -v `pwd`:/mnt python python
/mnt/test.py
[Fix]
Import the right pieces from AUFS to properly support the fix and get
rid of the AUFS dependency across all our kernels and re-apply the
overlayfs fix without the AUFS dependency.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs, especially when containers are used.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983640/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983640] Re: refactoring of overlayfs fix to properly support shiftfs
This bug is awaiting verification that the linux-ibm/5.15.0-1014.16
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-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.
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!
--
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/1983640
Title:
refactoring of overlayfs fix to properly support shiftfs
Status in linux package in Ubuntu:
Fix Committed
Status in linux-hwe-5.17 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux-hwe-5.17 source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
Fix Committed
Status in linux-hwe-5.17 source package in Kinetic:
Invalid
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch is required to use overlayfs on top of shiftfs and without
this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
However, we made this patch dependent on AUFS, starting with Jammy
we're not enabling AUFS anymore, so this fix becomes a no-op.
So we need to re-introduce this fix with a bit of refactoring to not
depend on AUFS.
[Test case]
The following script can be used to trigger the issue:
#!/bin/bash
cat > test.py << EOF
import sys
f = open("/proc/self/maps")
for l in f.readlines():
if "python" not in l:
continue
print(l)
s = l.split()
start, end = s[0].split("-")
fname = s[-1]
print(start, end, fname)
break
else:
sys.exit(1)
test_file1 = open(fname)
test_file2 = open("/proc/self/map_files/%s-%s" % (start, end))
fdinfo1 = open("/proc/self/fdinfo/%d" % test_file1.fileno()).read()
fdinfo2 = open("/proc/self/fdinfo/%d" % test_file2.fileno()).read()
if fdinfo1 != fdinfo2:
print("FAIL")
print(test_file1)
print(fdinfo1)
print(test_file2)
print(fdinfo2)
sys.exit(1)
print("PASS")
EOF
sudo docker run -it --privileged --rm -v `pwd`:/mnt python python
/mnt/test.py
[Fix]
Import the right pieces from AUFS to properly support the fix and get
rid of the AUFS dependency across all our kernels and re-apply the
overlayfs fix without the AUFS dependency.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs, especially when containers are used.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983640/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983640] Re: refactoring of overlayfs fix to properly support shiftfs
This bug is awaiting verification that the linux-oracle/5.15.0-1018.23
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-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.
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!
--
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/1983640
Title:
refactoring of overlayfs fix to properly support shiftfs
Status in linux package in Ubuntu:
Fix Committed
Status in linux-hwe-5.17 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux-hwe-5.17 source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
Fix Committed
Status in linux-hwe-5.17 source package in Kinetic:
Invalid
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch is required to use overlayfs on top of shiftfs and without
this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
However, we made this patch dependent on AUFS, starting with Jammy
we're not enabling AUFS anymore, so this fix becomes a no-op.
So we need to re-introduce this fix with a bit of refactoring to not
depend on AUFS.
[Test case]
The following script can be used to trigger the issue:
#!/bin/bash
cat > test.py << EOF
import sys
f = open("/proc/self/maps")
for l in f.readlines():
if "python" not in l:
continue
print(l)
s = l.split()
start, end = s[0].split("-")
fname = s[-1]
print(start, end, fname)
break
else:
sys.exit(1)
test_file1 = open(fname)
test_file2 = open("/proc/self/map_files/%s-%s" % (start, end))
fdinfo1 = open("/proc/self/fdinfo/%d" % test_file1.fileno()).read()
fdinfo2 = open("/proc/self/fdinfo/%d" % test_file2.fileno()).read()
if fdinfo1 != fdinfo2:
print("FAIL")
print(test_file1)
print(fdinfo1)
print(test_file2)
print(fdinfo2)
sys.exit(1)
print("PASS")
EOF
sudo docker run -it --privileged --rm -v `pwd`:/mnt python python
/mnt/test.py
[Fix]
Import the right pieces from AUFS to properly support the fix and get
rid of the AUFS dependency across all our kernels and re-apply the
overlayfs fix without the AUFS dependency.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs, especially when containers are used.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983640/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983640] Re: refactoring of overlayfs fix to properly support shiftfs
This bug was fixed in the package linux - 5.15.0-48.54 --- linux (5.15.0-48.54) jammy; urgency=medium * jammy/linux: 5.15.0-48.54 -proposed tracker (LP: #1987775) * System freeze after resuming from suspend due to PCI ASPM settings (LP: #1980829) - SAUCE: PCI/ASPM: Save/restore L1SS Capability for suspend/resume - SAUCE: whitelist platforms that needs save/restore ASPM L1SS for suspend/resume * [SRU][J/OEM-5.17][PATCH 0/1] Fix oled brightness set above frame-average luminance (LP: #1978986) - SAUCE: drm: New function to get luminance range based on static hdr metadata - SAUCE: drm/amdgpu_dm: Rely on split out luminance calculation function - SAUCE: drm/i915: Use luminance range calculated during edid parsing * Jammy: Add OVS Internal Port HW Offload to mlx5 driver (LP: #1983498) - net/mlx5e: Refactor rx handler of represetor device - net/mlx5e: Use generic name for the forwarding dev pointer - net/mlx5: E-Switch, Add ovs internal port mapping to metadata support - net/mlx5e: Support accept action - net/mlx5e: Accept action skbedit in the tc actions list - net/mlx5e: Offload tc rules that redirect to ovs internal port - net/mlx5e: Offload internal port as encap route device - net/mlx5e: Enable TC offload for ingress MACVLAN - net/mlx5e: Add indirect tc offload of ovs internal port - net/mlx5e: Term table handling of internal port rules - net/mlx5: Support internal port as decap route device - net/mlx5: Fix some error handling paths in 'mlx5e_tc_add_fdb_flow()' - net/mlx5e: TC, Fix memory leak with rules with internal port - net/mlx5e: Fix skb memory leak when TC classifier action offloads are disabled - net/mlx5e: Fix nullptr on deleting mirroring rule - net/mlx5e: Avoid implicit modify hdr for decap drop rule - net/mlx5e: Fix wrong source vport matching on tunnel rule - net/mlx5e: TC, fix decap fallback to uplink when int port not supported * Remove unused variable from i915 psr (LP: #1986798) - SAUCE: drm/i915/display/psr: Remove unused variable * refactoring of overlayfs fix to properly support shiftfs (LP: #1983640) - SAUCE: overlayfs: remove CONFIG_AUFS_FS dependency * Jammy update: v5.15.53 upstream stable release (LP: #1986728) - Revert "drm/amdgpu/display: set vblank_disable_immediate for DC" - drm/amdgpu: To flush tlb for MMHUB of RAVEN series - ksmbd: set the range of bytes to zero without extending file size in FSCTL_ZERO_DATA - ksmbd: check invalid FileOffset and BeyondFinalZero in FSCTL_ZERO_DATA - ksmbd: use vfs_llseek instead of dereferencing NULL - ipv6: take care of disable_policy when restoring routes - net: phy: Don't trigger state machine while in suspend - nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA XPG SX6000LNP (AKA SPECTRIX S40G) - nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA IM2P33F8ABR1 - nvdimm: Fix badblocks clear off-by-one error - powerpc/prom_init: Fix kernel config grep - powerpc/book3e: Fix PUD allocation size in map_kernel_page() - powerpc/bpf: Fix use of user_pt_regs in uapi - dm raid: fix accesses beyond end of raid member array - dm raid: fix KASAN warning in raid5_add_disks - s390/archrandom: simplify back to earlier design and initialize earlier - SUNRPC: Fix READ_PLUS crasher - net: rose: fix UAF bugs caused by timer handler - net: usb: ax88179_178a: Fix packet receiving - virtio-net: fix race between ndo_open() and virtio_device_ready() - selftests/net: pass ipv6_args to udpgso_bench's IPv6 TCP test - net: dsa: bcm_sf2: force pause link settings - net: tun: unlink NAPI from device on destruction - net: tun: stop NAPI when detaching queues - net: dp83822: disable false carrier interrupt - net: dp83822: disable rx error interrupt - RDMA/qedr: Fix reporting QP timeout attribute - RDMA/cm: Fix memory leak in ib_cm_insert_listen - linux/dim: Fix divide by 0 in RDMA DIM - net: usb: asix: do not force pause frames support - usbnet: fix memory allocation in helpers - selftests: mptcp: more stable diag tests - net: ipv6: unexport __init-annotated seg6_hmac_net_init() - NFSD: restore EINVAL error translation in nfsd_commit() - vfs: fix copy_file_range() regression in cross-fs copies - caif_virtio: fix race between virtio_device_ready() and ndo_open() - PM / devfreq: exynos-ppmu: Fix refcount leak in of_get_devfreq_events - vdpa/mlx5: Update Control VQ callback information - s390: remove unneeded 'select BUILD_BIN2C' - netfilter: nft_dynset: restore set element counter when failing to update - net/dsa/hirschmann: Add missing of_node_get() in hellcreek_led_setup() - net/sched: act_api: Notify user space if any actions were flushed before error - net: asix: fix "can't send until first packet is send" issue - net: bonding: fix possible
[Kernel-packages] [Bug 1983640] Re: refactoring of overlayfs fix to properly support shiftfs
This bug is awaiting verification that the linux-nvidia/5.15.0-1006.6
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-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.
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!
--
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/1983640
Title:
refactoring of overlayfs fix to properly support shiftfs
Status in linux package in Ubuntu:
Fix Committed
Status in linux-hwe-5.17 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux-hwe-5.17 source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
Fix Committed
Status in linux-hwe-5.17 source package in Kinetic:
Invalid
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch is required to use overlayfs on top of shiftfs and without
this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
However, we made this patch dependent on AUFS, starting with Jammy
we're not enabling AUFS anymore, so this fix becomes a no-op.
So we need to re-introduce this fix with a bit of refactoring to not
depend on AUFS.
[Test case]
The following script can be used to trigger the issue:
#!/bin/bash
cat > test.py << EOF
import sys
f = open("/proc/self/maps")
for l in f.readlines():
if "python" not in l:
continue
print(l)
s = l.split()
start, end = s[0].split("-")
fname = s[-1]
print(start, end, fname)
break
else:
sys.exit(1)
test_file1 = open(fname)
test_file2 = open("/proc/self/map_files/%s-%s" % (start, end))
fdinfo1 = open("/proc/self/fdinfo/%d" % test_file1.fileno()).read()
fdinfo2 = open("/proc/self/fdinfo/%d" % test_file2.fileno()).read()
if fdinfo1 != fdinfo2:
print("FAIL")
print(test_file1)
print(fdinfo1)
print(test_file2)
print(fdinfo2)
sys.exit(1)
print("PASS")
EOF
sudo docker run -it --privileged --rm -v `pwd`:/mnt python python
/mnt/test.py
[Fix]
Import the right pieces from AUFS to properly support the fix and get
rid of the AUFS dependency across all our kernels and re-apply the
overlayfs fix without the AUFS dependency.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs, especially when containers are used.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983640/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983640] Re: refactoring of overlayfs fix to properly support shiftfs
This bug is awaiting verification that the linux/5.15.0-48.54 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-jammy' to 'verification-done-jammy'. If the problem
still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.
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!
--
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/1983640
Title:
refactoring of overlayfs fix to properly support shiftfs
Status in linux package in Ubuntu:
Fix Committed
Status in linux-hwe-5.17 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux-hwe-5.17 source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
Fix Committed
Status in linux-hwe-5.17 source package in Kinetic:
Invalid
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch is required to use overlayfs on top of shiftfs and without
this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
However, we made this patch dependent on AUFS, starting with Jammy
we're not enabling AUFS anymore, so this fix becomes a no-op.
So we need to re-introduce this fix with a bit of refactoring to not
depend on AUFS.
[Test case]
The following script can be used to trigger the issue:
#!/bin/bash
cat > test.py << EOF
import sys
f = open("/proc/self/maps")
for l in f.readlines():
if "python" not in l:
continue
print(l)
s = l.split()
start, end = s[0].split("-")
fname = s[-1]
print(start, end, fname)
break
else:
sys.exit(1)
test_file1 = open(fname)
test_file2 = open("/proc/self/map_files/%s-%s" % (start, end))
fdinfo1 = open("/proc/self/fdinfo/%d" % test_file1.fileno()).read()
fdinfo2 = open("/proc/self/fdinfo/%d" % test_file2.fileno()).read()
if fdinfo1 != fdinfo2:
print("FAIL")
print(test_file1)
print(fdinfo1)
print(test_file2)
print(fdinfo2)
sys.exit(1)
print("PASS")
EOF
sudo docker run -it --privileged --rm -v `pwd`:/mnt python python
/mnt/test.py
[Fix]
Import the right pieces from AUFS to properly support the fix and get
rid of the AUFS dependency across all our kernels and re-apply the
overlayfs fix without the AUFS dependency.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs, especially when containers are used.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983640/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983640] Re: refactoring of overlayfs fix to properly support shiftfs
** Changed in: linux-hwe-5.17 (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
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/1983640
Title:
refactoring of overlayfs fix to properly support shiftfs
Status in linux package in Ubuntu:
Fix Committed
Status in linux-hwe-5.17 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Committed
Status in linux-hwe-5.17 source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
Fix Committed
Status in linux-hwe-5.17 source package in Kinetic:
Invalid
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch is required to use overlayfs on top of shiftfs and without
this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
However, we made this patch dependent on AUFS, starting with Jammy
we're not enabling AUFS anymore, so this fix becomes a no-op.
So we need to re-introduce this fix with a bit of refactoring to not
depend on AUFS.
[Test case]
The following script can be used to trigger the issue:
#!/bin/bash
cat > test.py << EOF
import sys
f = open("/proc/self/maps")
for l in f.readlines():
if "python" not in l:
continue
print(l)
s = l.split()
start, end = s[0].split("-")
fname = s[-1]
print(start, end, fname)
break
else:
sys.exit(1)
test_file1 = open(fname)
test_file2 = open("/proc/self/map_files/%s-%s" % (start, end))
fdinfo1 = open("/proc/self/fdinfo/%d" % test_file1.fileno()).read()
fdinfo2 = open("/proc/self/fdinfo/%d" % test_file2.fileno()).read()
if fdinfo1 != fdinfo2:
print("FAIL")
print(test_file1)
print(fdinfo1)
print(test_file2)
print(fdinfo2)
sys.exit(1)
print("PASS")
EOF
sudo docker run -it --privileged --rm -v `pwd`:/mnt python python
/mnt/test.py
[Fix]
Import the right pieces from AUFS to properly support the fix and get
rid of the AUFS dependency across all our kernels and re-apply the
overlayfs fix without the AUFS dependency.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs, especially when containers are used.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983640/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983640] Re: refactoring of overlayfs fix to properly support shiftfs
** Also affects: linux-hwe-5.17 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-hwe-5.17 (Ubuntu Kinetic)
Status: New => Invalid
** Changed in: linux (Ubuntu Kinetic)
Status: In Progress => Fix Committed
** Changed in: linux-hwe-5.17 (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-hwe-5.17 (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
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/1983640
Title:
refactoring of overlayfs fix to properly support shiftfs
Status in linux package in Ubuntu:
Fix Committed
Status in linux-hwe-5.17 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
In Progress
Status in linux-hwe-5.17 source package in Jammy:
Fix Committed
Status in linux source package in Kinetic:
Fix Committed
Status in linux-hwe-5.17 source package in Kinetic:
Invalid
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch is required to use overlayfs on top of shiftfs and without
this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
However, we made this patch dependent on AUFS, starting with Jammy
we're not enabling AUFS anymore, so this fix becomes a no-op.
So we need to re-introduce this fix with a bit of refactoring to not
depend on AUFS.
[Test case]
The following script can be used to trigger the issue:
#!/bin/bash
cat > test.py << EOF
import sys
f = open("/proc/self/maps")
for l in f.readlines():
if "python" not in l:
continue
print(l)
s = l.split()
start, end = s[0].split("-")
fname = s[-1]
print(start, end, fname)
break
else:
sys.exit(1)
test_file1 = open(fname)
test_file2 = open("/proc/self/map_files/%s-%s" % (start, end))
fdinfo1 = open("/proc/self/fdinfo/%d" % test_file1.fileno()).read()
fdinfo2 = open("/proc/self/fdinfo/%d" % test_file2.fileno()).read()
if fdinfo1 != fdinfo2:
print("FAIL")
print(test_file1)
print(fdinfo1)
print(test_file2)
print(fdinfo2)
sys.exit(1)
print("PASS")
EOF
sudo docker run -it --privileged --rm -v `pwd`:/mnt python python
/mnt/test.py
[Fix]
Import the right pieces from AUFS to properly support the fix and get
rid of the AUFS dependency across all our kernels and re-apply the
overlayfs fix without the AUFS dependency.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs, especially when containers are used.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983640/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983640] Re: refactoring of overlayfs fix to properly support shiftfs
** Changed in: linux (Ubuntu Jammy)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Kinetic)
Status: Incomplete => In Progress
--
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/1983640
Title:
refactoring of overlayfs fix to properly support shiftfs
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Jammy:
In Progress
Status in linux source package in Kinetic:
In Progress
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch is required to use overlayfs on top of shiftfs and without
this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
However, we made this patch dependent on AUFS, starting with Jammy
we're not enabling AUFS anymore, so this fix becomes a no-op.
So we need to re-introduce this fix with a bit of refactoring to not
depend on AUFS.
[Test case]
The following script can be used to trigger the issue:
#!/bin/bash
cat > test.py << EOF
import sys
f = open("/proc/self/maps")
for l in f.readlines():
if "python" not in l:
continue
print(l)
s = l.split()
start, end = s[0].split("-")
fname = s[-1]
print(start, end, fname)
break
else:
sys.exit(1)
test_file1 = open(fname)
test_file2 = open("/proc/self/map_files/%s-%s" % (start, end))
fdinfo1 = open("/proc/self/fdinfo/%d" % test_file1.fileno()).read()
fdinfo2 = open("/proc/self/fdinfo/%d" % test_file2.fileno()).read()
if fdinfo1 != fdinfo2:
print("FAIL")
print(test_file1)
print(fdinfo1)
print(test_file2)
print(fdinfo2)
sys.exit(1)
print("PASS")
EOF
sudo docker run -it --privileged --rm -v `pwd`:/mnt python python
/mnt/test.py
[Fix]
Import the right pieces from AUFS to properly support the fix and get
rid of the AUFS dependency across all our kernels and re-apply the
overlayfs fix without the AUFS dependency.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions
in overlayfs, especially when containers are used.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983640/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1983640] Re: refactoring of overlayfs fix to properly support shiftfs
** Summary changed:
- refactoring of overlayfs fix to report the right mnt_id of files opened from
map_files
+ refactoring of overlayfs fix to properly support shiftfs
** Description changed:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce patch:
- UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from
+ UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from
map_files
This patch is required to use overlayfs on top of shiftfs and without
this patch we may break containers that rely on shiftfs (using zfs/ceph
as storage pool w/ shiftfs enabled).
However, we made this patch dependent on AUFS, starting with Jammy we're
not enabling AUFS anymore, so this fix becomes a no-op.
So we need to re-introduce this fix with a bit of refactoring to not
depend on AUFS.
[Test case]
The following script can be used to trigger the issue:
- #!/bin/bash
+ #!/bin/bash
- cat > test.py << EOF
- import sys
+ cat > test.py << EOF
+ import sys
- f = open("/proc/self/maps")
+ f = open("/proc/self/maps")
- for l in f.readlines():
- if "python" not in l:
- continue
- print(l)
- s = l.split()
- start, end = s[0].split("-")
- fname = s[-1]
- print(start, end, fname)
- break
- else:
- sys.exit(1)
+ for l in f.readlines():
+ if "python" not in l:
+ continue
+ print(l)
+ s = l.split()
+ start, end = s[0].split("-")
+ fname = s[-1]
+ print(start, end, fname)
+ break
+ else:
+ sys.exit(1)
- test_file1 = open(fname)
- test_file2 = open("/proc/self/map_files/%s-%s" % (start, end))
+ test_file1 = open(fname)
+ test_file2 = open("/proc/self/map_files/%s-%s" % (start, end))
- fdinfo1 = open("/proc/self/fdinfo/%d" % test_file1.fileno()).read()
- fdinfo2 = open("/proc/self/fdinfo/%d" % test_file2.fileno()).read()
+ fdinfo1 = open("/proc/self/fdinfo/%d" % test_file1.fileno()).read()
+ fdinfo2 = open("/proc/self/fdinfo/%d" % test_file2.fileno()).read()
- if fdinfo1 != fdinfo2:
- print("FAIL")
- print(test_file1)
- print(fdinfo1)
- print(test_file2)
- print(fdinfo2)
- sys.exit(1)
- print("PASS")
- EOF
- sudo docker run -it --privileged --rm -v `pwd`:/mnt python python
/mnt/test.py
+ if fdinfo1 != fdinfo2:
+ print("FAIL")
+ print(test_file1)
+ print(fdinfo1)
+ print(test_file2)
+ print(fdinfo2)
+ sys.exit(1)
+ print("PASS")
+ EOF
+ sudo docker run -it --privileged --rm -v `pwd`:/mnt python python
/mnt/test.py
[Fix]
- Import the right pieces from AUFS to properly support the fix and get
- rid of the AUFS dependency across all our kernels.
+ Import the right pieces from AUFS to properly support the fix and get
+ rid of the AUFS dependency across all our kernels and re-apply the
+ overlayfs fix without the AUFS dependency.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions in
overlayfs, especially when containers are used.
--
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/1983640
Title:
refactoring of overlayfs fix to properly support shiftfs
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Jammy:
Incomplete
Status in linux source package in Kinetic:
Incomplete
Bug description:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce
patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened
from map_files
This patch is required to use overlayfs on top of shiftfs and without
this patch we may break containers that rely on shiftfs (using
zfs/ceph as storage pool w/ shiftfs enabled).
However, we made this patch dependent on AUFS, starting with Jammy
we're not enabling AUFS anymore, so this fix becomes a no-op.
So we need to re-introduce this fix with a bit of refactoring to not
depend on AUFS.
[Test case]
The following script can be used to trigger the issue:
#!/bin/bash
cat > test.py << EOF
import sys
f = open("/proc/self/maps")
for l in f.readlines():
if "python" not in l:
continue
print(l)
s = l.split()
start, end = s[0].split("-")
fname = s[-1]
print(start, end, fname)
break
else:
sys.exit(1)
test_file1 = open(fname)
test_file2 = open("/proc/self/map_files/%s-%s" % (start, end))
fdinfo1 = open("/proc/self/fdinfo/%d" % test_file1.fileno()).read()
fdinfo2 = open("/proc/self/fdinfo/%d" % test_file2.fileno()).read()
if fdinfo1 != fdinfo2:
print("FAIL")
print(test_file1)
print(fdinfo1)
print(test_file2)
print(fdinfo2)
sys.exit(1)
print("PASS")
EOF
sudo docker run -it --privileged --rm -v `pwd`:/mnt python python
/mnt/test.py
