| 2020-01-15 12:54:34 |
Mauricio Faria de Oliveira |
bug |
|
|
added bug |
| 2020-01-15 12:54:46 |
Mauricio Faria de Oliveira |
gfs2-utils (Ubuntu): status |
New |
Confirmed |
|
| 2020-01-15 12:54:49 |
Mauricio Faria de Oliveira |
gfs2-utils (Ubuntu): importance |
Undecided |
Medium |
|
| 2020-01-15 12:54:53 |
Mauricio Faria de Oliveira |
gfs2-utils (Ubuntu): assignee |
|
Mauricio Faria de Oliveira (mfo) |
|
| 2020-01-15 12:55:02 |
Mauricio Faria de Oliveira |
nominated for series |
|
Ubuntu Focal |
|
| 2020-01-15 12:55:02 |
Mauricio Faria de Oliveira |
bug task added |
|
gfs2-utils (Ubuntu Focal) |
|
| 2020-01-15 12:55:02 |
Mauricio Faria de Oliveira |
nominated for series |
|
Ubuntu Eoan |
|
| 2020-01-15 12:55:02 |
Mauricio Faria de Oliveira |
bug task added |
|
gfs2-utils (Ubuntu Eoan) |
|
| 2020-01-15 12:55:09 |
Mauricio Faria de Oliveira |
gfs2-utils (Ubuntu Eoan): status |
New |
Confirmed |
|
| 2020-01-15 12:55:13 |
Mauricio Faria de Oliveira |
gfs2-utils (Ubuntu Eoan): importance |
Undecided |
Medium |
|
| 2020-01-15 12:55:16 |
Mauricio Faria de Oliveira |
gfs2-utils (Ubuntu Eoan): assignee |
|
Mauricio Faria de Oliveira (mfo) |
|
| 2020-01-15 17:32:22 |
Mauricio Faria de Oliveira |
description |
The gfs2_jadd command (used in debian/tests/corosync)
fails with ENOTTY ("Inappropriate ioctl for device")
when the i386 packages are run on an amd64 kernel.
The i386 kernel has gone away, only amd64 is available:
- The i386 kernel build is dropped as of 5.3.0-16.17:
* Drop i386 build for 19.10 (LP: #1845714)
- Only linux-libc-dev:i386 is still built as of 5.3.0-17.18
* Re-enable linux-libc-dev build on i386 (LP: #1846508)
The last passing autopkgtests for gfs2-utils:i386 are on 5.3.0-13.14 built for i386.
The same kernel version built for amd64 _fails_.
(so it's potentially user/kernel interface, or kernel-only.)
- i386/i686)
# uname -rvm
5.3.0-13-generic #14-Ubuntu SMP Tue Sep 24 02:43:47 UTC 2019 i686
root@sf256930ei:~# gfs2_jadd -j 1 /mnt
Filesystem: /mnt
Old journals: 2
New journals: 3
- amd64/x86_64)
# uname -rvm
5.3.0-13-generic #14-Ubuntu SMP Tue Sep 24 02:46:08 UTC 2019 x86_64
# gfs2_jadd -j 1 /mnt
GETFLAGS: Inappropriate ioctl for device |
[Impact]
* The gfs2_jadd command (used in debian/tests/corosync)
fails with ENOTTY ("Inappropriate ioctl for device")
when the i386 packages are run on an amd64 kernel.
* The i386 kernel is gone, only amd64 is available.
* The fix introduced the compat ioctl()s for gfs2,
which landed in v5.5-rc1 thus not in Eoan/Focal.
[Test Case]
* The test steps are detailed in comment #2
based on gfs2-utils:debian/tests/corosync,
modified to be simpler and to fail either
with ENOTTY (failure) or ENOSPC (success).
[Regression Potential]
* The previous surface for this problem is
likely low, as i386 arch installs (which
is not as popular/widely used as amd64
nowadays) probably used the i386 kernel.
* The amd64-only kernel version released
is 5.3.0-17.18 dated 2019-10-10; gives
~3 month window to mind January 2020.
* So, behavior changes could theoretically
be seen on i386 installs where gfs2-utils
failed with ENOTTY and now all works fine
or fail differently (e.g. see test-case).
[Original Description]
The gfs2_jadd command (used in debian/tests/corosync)
fails with ENOTTY ("Inappropriate ioctl for device")
when the i386 packages are run on an amd64 kernel.
The i386 kernel has gone away, only amd64 is available:
- The i386 kernel build is dropped as of 5.3.0-15.16:
* Drop i386 build for 19.10 (LP: #1845714)
- Only linux-libc-dev:i386 is still built as of 5.3.0-17.18
* Re-enable linux-libc-dev build on i386 (LP: #1846508)
The last passing autopkgtests for gfs2-utils:i386 are on 5.3.0-13.14 built for i386.
The same kernel version built for amd64 _fails_.
(so it's potentially user/kernel interface, or kernel-only.)
- i386/i686)
# uname -rvm
5.3.0-13-generic #14-Ubuntu SMP Tue Sep 24 02:43:47 UTC 2019 i686
root@sf256930ei:~# gfs2_jadd -j 1 /mnt
Filesystem: /mnt
Old journals: 2
New journals: 3
- amd64/x86_64)
# uname -rvm
5.3.0-13-generic #14-Ubuntu SMP Tue Sep 24 02:46:08 UTC 2019 x86_64
# gfs2_jadd -j 1 /mnt
GETFLAGS: Inappropriate ioctl for device |
|
| 2020-01-15 17:32:45 |
Mauricio Faria de Oliveira |
description |
[Impact]
* The gfs2_jadd command (used in debian/tests/corosync)
fails with ENOTTY ("Inappropriate ioctl for device")
when the i386 packages are run on an amd64 kernel.
* The i386 kernel is gone, only amd64 is available.
* The fix introduced the compat ioctl()s for gfs2,
which landed in v5.5-rc1 thus not in Eoan/Focal.
[Test Case]
* The test steps are detailed in comment #2
based on gfs2-utils:debian/tests/corosync,
modified to be simpler and to fail either
with ENOTTY (failure) or ENOSPC (success).
[Regression Potential]
* The previous surface for this problem is
likely low, as i386 arch installs (which
is not as popular/widely used as amd64
nowadays) probably used the i386 kernel.
* The amd64-only kernel version released
is 5.3.0-17.18 dated 2019-10-10; gives
~3 month window to mind January 2020.
* So, behavior changes could theoretically
be seen on i386 installs where gfs2-utils
failed with ENOTTY and now all works fine
or fail differently (e.g. see test-case).
[Original Description]
The gfs2_jadd command (used in debian/tests/corosync)
fails with ENOTTY ("Inappropriate ioctl for device")
when the i386 packages are run on an amd64 kernel.
The i386 kernel has gone away, only amd64 is available:
- The i386 kernel build is dropped as of 5.3.0-15.16:
* Drop i386 build for 19.10 (LP: #1845714)
- Only linux-libc-dev:i386 is still built as of 5.3.0-17.18
* Re-enable linux-libc-dev build on i386 (LP: #1846508)
The last passing autopkgtests for gfs2-utils:i386 are on 5.3.0-13.14 built for i386.
The same kernel version built for amd64 _fails_.
(so it's potentially user/kernel interface, or kernel-only.)
- i386/i686)
# uname -rvm
5.3.0-13-generic #14-Ubuntu SMP Tue Sep 24 02:43:47 UTC 2019 i686
root@sf256930ei:~# gfs2_jadd -j 1 /mnt
Filesystem: /mnt
Old journals: 2
New journals: 3
- amd64/x86_64)
# uname -rvm
5.3.0-13-generic #14-Ubuntu SMP Tue Sep 24 02:46:08 UTC 2019 x86_64
# gfs2_jadd -j 1 /mnt
GETFLAGS: Inappropriate ioctl for device |
[Impact]
* The gfs2_jadd command (used in debian/tests/corosync)
fails with ENOTTY ("Inappropriate ioctl for device")
when the i386 packages are run on an amd64 kernel.
* The i386 kernel is gone, only amd64 is available.
* The fix introduces the compat ioctl()s for gfs2,
which landed in v5.5-rc1 thus not in Eoan/Focal.
[Test Case]
* The test steps are detailed in comment #2
based on gfs2-utils:debian/tests/corosync,
modified to be simpler and to fail either
with ENOTTY (failure) or ENOSPC (success).
[Regression Potential]
* The previous surface for this problem is
likely low, as i386 arch installs (which
is not as popular/widely used as amd64
nowadays) probably used the i386 kernel.
* The amd64-only kernel version released
is 5.3.0-17.18 dated 2019-10-10; gives
~3 month window to mind January 2020.
* So, behavior changes could theoretically
be seen on i386 installs where gfs2-utils
failed with ENOTTY and now all works fine
or fail differently (e.g. see test-case).
[Original Description]
The gfs2_jadd command (used in debian/tests/corosync)
fails with ENOTTY ("Inappropriate ioctl for device")
when the i386 packages are run on an amd64 kernel.
The i386 kernel has gone away, only amd64 is available:
- The i386 kernel build is dropped as of 5.3.0-15.16:
* Drop i386 build for 19.10 (LP: #1845714)
- Only linux-libc-dev:i386 is still built as of 5.3.0-17.18
* Re-enable linux-libc-dev build on i386 (LP: #1846508)
The last passing autopkgtests for gfs2-utils:i386 are on 5.3.0-13.14 built for i386.
The same kernel version built for amd64 _fails_.
(so it's potentially user/kernel interface, or kernel-only.)
- i386/i686)
# uname -rvm
5.3.0-13-generic #14-Ubuntu SMP Tue Sep 24 02:43:47 UTC 2019 i686
root@sf256930ei:~# gfs2_jadd -j 1 /mnt
Filesystem: /mnt
Old journals: 2
New journals: 3
- amd64/x86_64)
# uname -rvm
5.3.0-13-generic #14-Ubuntu SMP Tue Sep 24 02:46:08 UTC 2019 x86_64
# gfs2_jadd -j 1 /mnt
GETFLAGS: Inappropriate ioctl for device |
|
| 2020-01-15 17:33:24 |
Mauricio Faria de Oliveira |
description |
[Impact]
* The gfs2_jadd command (used in debian/tests/corosync)
fails with ENOTTY ("Inappropriate ioctl for device")
when the i386 packages are run on an amd64 kernel.
* The i386 kernel is gone, only amd64 is available.
* The fix introduces the compat ioctl()s for gfs2,
which landed in v5.5-rc1 thus not in Eoan/Focal.
[Test Case]
* The test steps are detailed in comment #2
based on gfs2-utils:debian/tests/corosync,
modified to be simpler and to fail either
with ENOTTY (failure) or ENOSPC (success).
[Regression Potential]
* The previous surface for this problem is
likely low, as i386 arch installs (which
is not as popular/widely used as amd64
nowadays) probably used the i386 kernel.
* The amd64-only kernel version released
is 5.3.0-17.18 dated 2019-10-10; gives
~3 month window to mind January 2020.
* So, behavior changes could theoretically
be seen on i386 installs where gfs2-utils
failed with ENOTTY and now all works fine
or fail differently (e.g. see test-case).
[Original Description]
The gfs2_jadd command (used in debian/tests/corosync)
fails with ENOTTY ("Inappropriate ioctl for device")
when the i386 packages are run on an amd64 kernel.
The i386 kernel has gone away, only amd64 is available:
- The i386 kernel build is dropped as of 5.3.0-15.16:
* Drop i386 build for 19.10 (LP: #1845714)
- Only linux-libc-dev:i386 is still built as of 5.3.0-17.18
* Re-enable linux-libc-dev build on i386 (LP: #1846508)
The last passing autopkgtests for gfs2-utils:i386 are on 5.3.0-13.14 built for i386.
The same kernel version built for amd64 _fails_.
(so it's potentially user/kernel interface, or kernel-only.)
- i386/i686)
# uname -rvm
5.3.0-13-generic #14-Ubuntu SMP Tue Sep 24 02:43:47 UTC 2019 i686
root@sf256930ei:~# gfs2_jadd -j 1 /mnt
Filesystem: /mnt
Old journals: 2
New journals: 3
- amd64/x86_64)
# uname -rvm
5.3.0-13-generic #14-Ubuntu SMP Tue Sep 24 02:46:08 UTC 2019 x86_64
# gfs2_jadd -j 1 /mnt
GETFLAGS: Inappropriate ioctl for device |
[Impact]
* The gfs2_jadd command (used in debian/tests/corosync)
fails with ENOTTY ("Inappropriate ioctl for device")
when the i386 packages are run on an amd64 kernel.
* The i386 kernel is gone, only amd64 is available.
* The fix introduces the compat ioctl()s for gfs2,
which landed in v5.5-rc1 thus not in Eoan/Focal.
[Test Case]
* The test steps are detailed in comment #2
based on gfs2-utils:debian/tests/corosync,
modified to be simpler and to fail either
with ENOTTY (failure) or ENOSPC (success).
[Regression Potential]
* The previous surface for this problem is
likely low, as i386 arch installs (which
is not as popular/widely used as amd64
nowadays) probably used the i386 kernel.
* The amd64-only kernel version released
is 5.3.0-17.18 dated 2019-10-10; gives
~3 month window to mid January 2020.
* So, behavior changes could theoretically
be seen on i386 installs where gfs2-utils
failed with ENOTTY and now all works fine
or fail differently (e.g. see test-case).
[Original Description]
The gfs2_jadd command (used in debian/tests/corosync)
fails with ENOTTY ("Inappropriate ioctl for device")
when the i386 packages are run on an amd64 kernel.
The i386 kernel has gone away, only amd64 is available:
- The i386 kernel build is dropped as of 5.3.0-15.16:
* Drop i386 build for 19.10 (LP: #1845714)
- Only linux-libc-dev:i386 is still built as of 5.3.0-17.18
* Re-enable linux-libc-dev build on i386 (LP: #1846508)
The last passing autopkgtests for gfs2-utils:i386 are on 5.3.0-13.14 built for i386.
The same kernel version built for amd64 _fails_.
(so it's potentially user/kernel interface, or kernel-only.)
- i386/i686)
# uname -rvm
5.3.0-13-generic #14-Ubuntu SMP Tue Sep 24 02:43:47 UTC 2019 i686
root@sf256930ei:~# gfs2_jadd -j 1 /mnt
Filesystem: /mnt
Old journals: 2
New journals: 3
- amd64/x86_64)
# uname -rvm
5.3.0-13-generic #14-Ubuntu SMP Tue Sep 24 02:46:08 UTC 2019 x86_64
# gfs2_jadd -j 1 /mnt
GETFLAGS: Inappropriate ioctl for device |
|
| 2020-01-15 17:34:25 |
Mauricio Faria de Oliveira |
description |
[Impact]
* The gfs2_jadd command (used in debian/tests/corosync)
fails with ENOTTY ("Inappropriate ioctl for device")
when the i386 packages are run on an amd64 kernel.
* The i386 kernel is gone, only amd64 is available.
* The fix introduces the compat ioctl()s for gfs2,
which landed in v5.5-rc1 thus not in Eoan/Focal.
[Test Case]
* The test steps are detailed in comment #2
based on gfs2-utils:debian/tests/corosync,
modified to be simpler and to fail either
with ENOTTY (failure) or ENOSPC (success).
[Regression Potential]
* The previous surface for this problem is
likely low, as i386 arch installs (which
is not as popular/widely used as amd64
nowadays) probably used the i386 kernel.
* The amd64-only kernel version released
is 5.3.0-17.18 dated 2019-10-10; gives
~3 month window to mid January 2020.
* So, behavior changes could theoretically
be seen on i386 installs where gfs2-utils
failed with ENOTTY and now all works fine
or fail differently (e.g. see test-case).
[Original Description]
The gfs2_jadd command (used in debian/tests/corosync)
fails with ENOTTY ("Inappropriate ioctl for device")
when the i386 packages are run on an amd64 kernel.
The i386 kernel has gone away, only amd64 is available:
- The i386 kernel build is dropped as of 5.3.0-15.16:
* Drop i386 build for 19.10 (LP: #1845714)
- Only linux-libc-dev:i386 is still built as of 5.3.0-17.18
* Re-enable linux-libc-dev build on i386 (LP: #1846508)
The last passing autopkgtests for gfs2-utils:i386 are on 5.3.0-13.14 built for i386.
The same kernel version built for amd64 _fails_.
(so it's potentially user/kernel interface, or kernel-only.)
- i386/i686)
# uname -rvm
5.3.0-13-generic #14-Ubuntu SMP Tue Sep 24 02:43:47 UTC 2019 i686
root@sf256930ei:~# gfs2_jadd -j 1 /mnt
Filesystem: /mnt
Old journals: 2
New journals: 3
- amd64/x86_64)
# uname -rvm
5.3.0-13-generic #14-Ubuntu SMP Tue Sep 24 02:46:08 UTC 2019 x86_64
# gfs2_jadd -j 1 /mnt
GETFLAGS: Inappropriate ioctl for device |
[Impact]
* The gfs2_jadd command (used in debian/tests/corosync)
fails with ENOTTY ("Inappropriate ioctl for device")
when the i386 packages are run on an amd64 kernel.
* The i386 kernel is gone, only amd64 is available.
* The fix introduces the compat ioctl()s for gfs2,
which landed in v5.5-rc1 thus not in Eoan/Focal.
[Test Case]
* The test steps are detailed in comment #2
based on gfs2-utils:debian/tests/corosync,
modified to be simpler and to fail either
with ENOTTY (failure) or ENOSPC (success).
[Regression Potential]
* The previous surface for this problem is
likely low, as i386 arch installs (which
is not as popular/widely used as amd64
nowadays) probably used the i386 kernel.
* The amd64-only kernel version released
is 5.3.0-17.18 dated 2019-10-10; gives
~3 month window to mid January 2020.
* So, behavior changes could theoretically
be seen on i386 installs with the newer
kernel which is amd64-only, wheregfs2-utils
failed with ENOTTY and now is working fine
or failing differently (e.g. see test-case).
[Original Description]
The gfs2_jadd command (used in debian/tests/corosync)
fails with ENOTTY ("Inappropriate ioctl for device")
when the i386 packages are run on an amd64 kernel.
The i386 kernel has gone away, only amd64 is available:
- The i386 kernel build is dropped as of 5.3.0-15.16:
* Drop i386 build for 19.10 (LP: #1845714)
- Only linux-libc-dev:i386 is still built as of 5.3.0-17.18
* Re-enable linux-libc-dev build on i386 (LP: #1846508)
The last passing autopkgtests for gfs2-utils:i386 are on 5.3.0-13.14 built for i386.
The same kernel version built for amd64 _fails_.
(so it's potentially user/kernel interface, or kernel-only.)
- i386/i686)
# uname -rvm
5.3.0-13-generic #14-Ubuntu SMP Tue Sep 24 02:43:47 UTC 2019 i686
root@sf256930ei:~# gfs2_jadd -j 1 /mnt
Filesystem: /mnt
Old journals: 2
New journals: 3
- amd64/x86_64)
# uname -rvm
5.3.0-13-generic #14-Ubuntu SMP Tue Sep 24 02:46:08 UTC 2019 x86_64
# gfs2_jadd -j 1 /mnt
GETFLAGS: Inappropriate ioctl for device |
|
| 2020-01-15 17:38:29 |
Mauricio Faria de Oliveira |
description |
[Impact]
* The gfs2_jadd command (used in debian/tests/corosync)
fails with ENOTTY ("Inappropriate ioctl for device")
when the i386 packages are run on an amd64 kernel.
* The i386 kernel is gone, only amd64 is available.
* The fix introduces the compat ioctl()s for gfs2,
which landed in v5.5-rc1 thus not in Eoan/Focal.
[Test Case]
* The test steps are detailed in comment #2
based on gfs2-utils:debian/tests/corosync,
modified to be simpler and to fail either
with ENOTTY (failure) or ENOSPC (success).
[Regression Potential]
* The previous surface for this problem is
likely low, as i386 arch installs (which
is not as popular/widely used as amd64
nowadays) probably used the i386 kernel.
* The amd64-only kernel version released
is 5.3.0-17.18 dated 2019-10-10; gives
~3 month window to mid January 2020.
* So, behavior changes could theoretically
be seen on i386 installs with the newer
kernel which is amd64-only, wheregfs2-utils
failed with ENOTTY and now is working fine
or failing differently (e.g. see test-case).
[Original Description]
The gfs2_jadd command (used in debian/tests/corosync)
fails with ENOTTY ("Inappropriate ioctl for device")
when the i386 packages are run on an amd64 kernel.
The i386 kernel has gone away, only amd64 is available:
- The i386 kernel build is dropped as of 5.3.0-15.16:
* Drop i386 build for 19.10 (LP: #1845714)
- Only linux-libc-dev:i386 is still built as of 5.3.0-17.18
* Re-enable linux-libc-dev build on i386 (LP: #1846508)
The last passing autopkgtests for gfs2-utils:i386 are on 5.3.0-13.14 built for i386.
The same kernel version built for amd64 _fails_.
(so it's potentially user/kernel interface, or kernel-only.)
- i386/i686)
# uname -rvm
5.3.0-13-generic #14-Ubuntu SMP Tue Sep 24 02:43:47 UTC 2019 i686
root@sf256930ei:~# gfs2_jadd -j 1 /mnt
Filesystem: /mnt
Old journals: 2
New journals: 3
- amd64/x86_64)
# uname -rvm
5.3.0-13-generic #14-Ubuntu SMP Tue Sep 24 02:46:08 UTC 2019 x86_64
# gfs2_jadd -j 1 /mnt
GETFLAGS: Inappropriate ioctl for device |
[Impact]
* The gfs2_jadd command (used in debian/tests/corosync)
fails with ENOTTY ("Inappropriate ioctl for device")
when the i386 packages are run on an amd64 kernel.
* The i386 kernel is gone, only amd64 is available.
* This breaks the autopkgtest of gfs2-utils:i386,
reporting false-negatives/regressions for many
of its dependencies, as they go into -proposed.
* The fix introduces the compat ioctl()s for gfs2,
which landed in v5.5-rc1 thus not in Eoan/Focal.
[Test Case]
* The test steps are detailed in comment #2
based on gfs2-utils:debian/tests/corosync,
modified to be simpler and to fail either
with ENOTTY (failure) or ENOSPC (success).
[Regression Potential]
* The previous surface for this problem is
likely low, as i386 arch installs (which
is not as popular/widely used as amd64
nowadays) probably used the i386 kernel.
* The amd64-only kernel version released
is 5.3.0-17.18 dated 2019-10-10; gives
~3 month window to mid January 2020.
* So, behavior changes could theoretically
be seen on i386 installs with the newer
kernel which is amd64-only, wheregfs2-utils
failed with ENOTTY and now is working fine
or failing differently (e.g. see test-case).
[Original Description]
The gfs2_jadd command (used in debian/tests/corosync)
fails with ENOTTY ("Inappropriate ioctl for device")
when the i386 packages are run on an amd64 kernel.
The i386 kernel has gone away, only amd64 is available:
- The i386 kernel build is dropped as of 5.3.0-15.16:
* Drop i386 build for 19.10 (LP: #1845714)
- Only linux-libc-dev:i386 is still built as of 5.3.0-17.18
* Re-enable linux-libc-dev build on i386 (LP: #1846508)
The last passing autopkgtests for gfs2-utils:i386 are on 5.3.0-13.14 built for i386.
The same kernel version built for amd64 _fails_.
(so it's potentially user/kernel interface, or kernel-only.)
- i386/i686)
# uname -rvm
5.3.0-13-generic #14-Ubuntu SMP Tue Sep 24 02:43:47 UTC 2019 i686
root@sf256930ei:~# gfs2_jadd -j 1 /mnt
Filesystem: /mnt
Old journals: 2
New journals: 3
- amd64/x86_64)
# uname -rvm
5.3.0-13-generic #14-Ubuntu SMP Tue Sep 24 02:46:08 UTC 2019 x86_64
# gfs2_jadd -j 1 /mnt
GETFLAGS: Inappropriate ioctl for device |
|
| 2020-01-15 17:38:56 |
Mauricio Faria de Oliveira |
gfs2-utils (Ubuntu Eoan): status |
Confirmed |
In Progress |
|
| 2020-01-15 17:38:58 |
Mauricio Faria de Oliveira |
gfs2-utils (Ubuntu Focal): status |
Confirmed |
In Progress |
|
| 2020-01-15 17:39:36 |
Mauricio Faria de Oliveira |
description |
[Impact]
* The gfs2_jadd command (used in debian/tests/corosync)
fails with ENOTTY ("Inappropriate ioctl for device")
when the i386 packages are run on an amd64 kernel.
* The i386 kernel is gone, only amd64 is available.
* This breaks the autopkgtest of gfs2-utils:i386,
reporting false-negatives/regressions for many
of its dependencies, as they go into -proposed.
* The fix introduces the compat ioctl()s for gfs2,
which landed in v5.5-rc1 thus not in Eoan/Focal.
[Test Case]
* The test steps are detailed in comment #2
based on gfs2-utils:debian/tests/corosync,
modified to be simpler and to fail either
with ENOTTY (failure) or ENOSPC (success).
[Regression Potential]
* The previous surface for this problem is
likely low, as i386 arch installs (which
is not as popular/widely used as amd64
nowadays) probably used the i386 kernel.
* The amd64-only kernel version released
is 5.3.0-17.18 dated 2019-10-10; gives
~3 month window to mid January 2020.
* So, behavior changes could theoretically
be seen on i386 installs with the newer
kernel which is amd64-only, wheregfs2-utils
failed with ENOTTY and now is working fine
or failing differently (e.g. see test-case).
[Original Description]
The gfs2_jadd command (used in debian/tests/corosync)
fails with ENOTTY ("Inappropriate ioctl for device")
when the i386 packages are run on an amd64 kernel.
The i386 kernel has gone away, only amd64 is available:
- The i386 kernel build is dropped as of 5.3.0-15.16:
* Drop i386 build for 19.10 (LP: #1845714)
- Only linux-libc-dev:i386 is still built as of 5.3.0-17.18
* Re-enable linux-libc-dev build on i386 (LP: #1846508)
The last passing autopkgtests for gfs2-utils:i386 are on 5.3.0-13.14 built for i386.
The same kernel version built for amd64 _fails_.
(so it's potentially user/kernel interface, or kernel-only.)
- i386/i686)
# uname -rvm
5.3.0-13-generic #14-Ubuntu SMP Tue Sep 24 02:43:47 UTC 2019 i686
root@sf256930ei:~# gfs2_jadd -j 1 /mnt
Filesystem: /mnt
Old journals: 2
New journals: 3
- amd64/x86_64)
# uname -rvm
5.3.0-13-generic #14-Ubuntu SMP Tue Sep 24 02:46:08 UTC 2019 x86_64
# gfs2_jadd -j 1 /mnt
GETFLAGS: Inappropriate ioctl for device |
[Impact]
* The gfs2_jadd command (used in debian/tests/corosync)
fails with ENOTTY ("Inappropriate ioctl for device")
when the i386 packages are run on an amd64 kernel.
* The i386 kernel is gone, only amd64 is available.
* The fix introduces the compat ioctl()s for gfs2,
which landed in v5.5-rc1 thus not in Eoan/Focal.
[Test Case]
* The test steps are detailed in comment #2
based on gfs2-utils:debian/tests/corosync,
modified to be simpler and to fail either
with ENOTTY (failure) or ENOSPC (success).
[Regression Potential]
* The previous surface for this problem is
likely low, as i386 arch installs (which
is not as popular/widely used as amd64
nowadays) probably used the i386 kernel.
* The amd64-only kernel version released
is 5.3.0-17.18 dated 2019-10-10; gives
~3 month window to mid January 2020.
* So, behavior changes could theoretically
be seen on i386 installs with the newer
kernel which is amd64-only, where gfs2-utils
failed with ENOTTY and now is working fine
or failing differently (e.g. see test-case).
[Original Description]
The gfs2_jadd command (used in debian/tests/corosync)
fails with ENOTTY ("Inappropriate ioctl for device")
when the i386 packages are run on an amd64 kernel.
The i386 kernel has gone away, only amd64 is available:
- The i386 kernel build is dropped as of 5.3.0-15.16:
* Drop i386 build for 19.10 (LP: #1845714)
- Only linux-libc-dev:i386 is still built as of 5.3.0-17.18
* Re-enable linux-libc-dev build on i386 (LP: #1846508)
The last passing autopkgtests for gfs2-utils:i386 are on 5.3.0-13.14 built for i386.
The same kernel version built for amd64 _fails_.
(so it's potentially user/kernel interface, or kernel-only.)
- i386/i686)
# uname -rvm
5.3.0-13-generic #14-Ubuntu SMP Tue Sep 24 02:43:47 UTC 2019 i686
root@sf256930ei:~# gfs2_jadd -j 1 /mnt
Filesystem: /mnt
Old journals: 2
New journals: 3
- amd64/x86_64)
# uname -rvm
5.3.0-13-generic #14-Ubuntu SMP Tue Sep 24 02:46:08 UTC 2019 x86_64
# gfs2_jadd -j 1 /mnt
GETFLAGS: Inappropriate ioctl for device |
|
| 2020-01-15 17:53:29 |
Rafael David Tinoco |
bug |
|
|
added subscriber Ubuntu Server High Availability |
| 2020-01-15 18:44:42 |
Mauricio Faria de Oliveira |
bug task added |
|
linux (Ubuntu) |
|
| 2020-01-15 18:44:52 |
Mauricio Faria de Oliveira |
linux (Ubuntu Eoan): status |
New |
In Progress |
|
| 2020-01-15 18:44:56 |
Mauricio Faria de Oliveira |
linux (Ubuntu Eoan): importance |
Undecided |
Medium |
|
| 2020-01-15 18:44:59 |
Mauricio Faria de Oliveira |
linux (Ubuntu Eoan): assignee |
|
Mauricio Faria de Oliveira (mfo) |
|
| 2020-01-15 18:45:04 |
Mauricio Faria de Oliveira |
linux (Ubuntu Focal): status |
New |
In Progress |
|
| 2020-01-15 18:45:08 |
Mauricio Faria de Oliveira |
linux (Ubuntu Focal): importance |
Undecided |
Medium |
|
| 2020-01-15 18:45:11 |
Mauricio Faria de Oliveira |
linux (Ubuntu Focal): assignee |
|
Mauricio Faria de Oliveira (mfo) |
|
| 2020-01-15 18:45:17 |
Mauricio Faria de Oliveira |
gfs2-utils (Ubuntu Eoan): status |
In Progress |
Invalid |
|
| 2020-01-15 18:45:23 |
Mauricio Faria de Oliveira |
gfs2-utils (Ubuntu Eoan): importance |
Medium |
Undecided |
|
| 2020-01-15 18:45:26 |
Mauricio Faria de Oliveira |
gfs2-utils (Ubuntu Eoan): assignee |
Mauricio Faria de Oliveira (mfo) |
|
|
| 2020-01-15 18:45:30 |
Mauricio Faria de Oliveira |
gfs2-utils (Ubuntu Focal): status |
In Progress |
Invalid |
|
| 2020-01-15 18:45:33 |
Mauricio Faria de Oliveira |
gfs2-utils (Ubuntu Focal): importance |
Medium |
Undecided |
|
| 2020-01-15 18:45:35 |
Mauricio Faria de Oliveira |
gfs2-utils (Ubuntu Focal): assignee |
Mauricio Faria de Oliveira (mfo) |
|
|
| 2020-01-21 23:08:49 |
Seth Forshee |
linux (Ubuntu Focal): status |
In Progress |
Fix Committed |
|
| 2020-01-28 19:25:50 |
Khaled El Mously |
linux (Ubuntu Eoan): status |
In Progress |
Fix Committed |
|
| 2020-02-03 22:44:50 |
Ubuntu Kernel Bot |
tags |
|
verification-needed-eoan |
|
| 2020-02-04 14:46:04 |
Mauricio Faria de Oliveira |
tags |
verification-needed-eoan |
verification-done-eoan |
|
| 2020-02-17 10:23:38 |
Launchpad Janitor |
linux (Ubuntu Eoan): status |
Fix Committed |
Fix Released |
|
| 2020-02-17 10:23:38 |
Launchpad Janitor |
cve linked |
|
2019-19050 |
|
| 2020-02-17 10:23:38 |
Launchpad Janitor |
cve linked |
|
2019-19077 |
|
| 2020-02-17 10:23:38 |
Launchpad Janitor |
cve linked |
|
2019-19078 |
|
| 2020-02-17 10:23:38 |
Launchpad Janitor |
cve linked |
|
2019-19082 |
|
| 2020-02-17 10:23:38 |
Launchpad Janitor |
cve linked |
|
2019-19332 |
|
| 2020-02-17 10:23:38 |
Launchpad Janitor |
cve linked |
|
2019-19965 |
|
| 2020-03-16 23:19:02 |
Launchpad Janitor |
linux (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2020-03-16 23:19:02 |
Launchpad Janitor |
cve linked |
|
2019-19076 |
|
