2022-08-05 06:05:43 |
Andrea Righi |
bug |
|
|
added bug |
2022-08-05 06:06:11 |
Andrea Righi |
nominated for series |
|
Ubuntu Focal |
|
2022-08-05 06:06:11 |
Andrea Righi |
bug task added |
|
linux (Ubuntu Focal) |
|
2022-08-05 06:06:11 |
Andrea Righi |
nominated for series |
|
Ubuntu Jammy |
|
2022-08-05 06:06:11 |
Andrea Righi |
bug task added |
|
linux (Ubuntu Jammy) |
|
2022-08-05 06:09:04 |
Andrea Righi |
nominated for series |
|
Ubuntu Kinetic |
|
2022-08-05 06:09:04 |
Andrea Righi |
bug task added |
|
linux (Ubuntu Kinetic) |
|
2022-08-05 06:16:11 |
Andrea Righi |
bug task deleted |
linux (Ubuntu Focal) |
|
|
2022-08-05 06:28:04 |
Andrea Righi |
summary |
refactoring of overlayfs fix to report the right mnt_id of files opened from map_files |
refactoring of overlayfs fix to properly support shiftfs |
|
2022-08-05 06:29:30 |
Andrea Righi |
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.
[Regression potential]
This patch is touching overlayfs, so we may see potential regressions in overlayfs, especially when containers are used. |
[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. |
|
2022-08-05 06:30:10 |
Ubuntu Kernel Bot |
linux (Ubuntu): status |
New |
Incomplete |
|
2022-08-05 06:30:13 |
Ubuntu Kernel Bot |
linux (Ubuntu Jammy): status |
New |
Incomplete |
|
2022-08-05 11:19:51 |
Kleber Sacilotto de Souza |
linux (Ubuntu Jammy): status |
Incomplete |
In Progress |
|
2022-08-05 11:19:54 |
Kleber Sacilotto de Souza |
linux (Ubuntu Kinetic): status |
Incomplete |
In Progress |
|
2022-08-17 09:02:23 |
Kleber Sacilotto de Souza |
bug task added |
|
linux-hwe-5.17 (Ubuntu) |
|
2022-08-17 09:02:30 |
Kleber Sacilotto de Souza |
linux-hwe-5.17 (Ubuntu Kinetic): status |
New |
Invalid |
|
2022-08-17 09:03:13 |
Kleber Sacilotto de Souza |
linux (Ubuntu Kinetic): status |
In Progress |
Fix Committed |
|
2022-08-17 09:03:18 |
Kleber Sacilotto de Souza |
linux-hwe-5.17 (Ubuntu Jammy): status |
New |
In Progress |
|
2022-08-17 09:06:46 |
Kleber Sacilotto de Souza |
linux-hwe-5.17 (Ubuntu Jammy): status |
In Progress |
Fix Committed |
|
2022-08-23 07:54:33 |
Stefan Bader |
linux-hwe-5.17 (Ubuntu Jammy): importance |
Undecided |
Medium |
|
2022-08-23 07:54:39 |
Stefan Bader |
linux (Ubuntu Jammy): importance |
Undecided |
Medium |
|
2022-08-23 07:56:09 |
Stefan Bader |
linux (Ubuntu Jammy): status |
In Progress |
Fix Committed |
|
2022-09-20 08:56:03 |
Launchpad Janitor |
linux (Ubuntu Jammy): status |
Fix Committed |
Fix Released |
|
2022-09-20 08:56:03 |
Launchpad Janitor |
cve linked |
|
2021-33655 |
|
2022-09-20 08:56:03 |
Launchpad Janitor |
cve linked |
|
2022-36946 |
|
2022-10-04 09:44:59 |
Launchpad Janitor |
linux (Ubuntu Kinetic): status |
Fix Committed |
Fix Released |
|
2022-10-04 09:44:59 |
Launchpad Janitor |
cve linked |
|
2022-2978 |
|
2022-10-22 23:54:59 |
Manuel Alejandro de Brito Fontes |
linux-hwe-5.17 (Ubuntu Kinetic): status |
Invalid |
Confirmed |
|
2022-12-07 15:49:45 |
Ubuntu Kernel Bot |
tags |
|
kernel-spammed-jammy-linux-bluefield verification-needed-jammy |
|