[Bug 2003250] Re: networkctl reload with bond devices causes slaves to go DOWN and UP, causing couple of seconds of network loss

[Ioanna Alifieraki]

** Description changed:

  [SRU TEMPLATE]
  
  [DESCRIPTION]
  
  We currently use Ubuntu 22.04.1 LTS including updates for our production 
cloud (switched from legacy Centos 7).
  Although we like the distribution we recently hit serious systemd buggy 
behavior described in [1] bugreport using packages [2].
  
  Unfortunatelly the clouds we are running consist of openstack on top of
  kubernetes and we need to have complex network configuration including
  linux bond devices.
  
  Our observation is that every time we apply our configuration via CI/CD
  infrastructure using ansible and netplan (regardless whether there is
  actual network configuration change) we see approximatelly 8-16 seconds
  network interruptions and see bond interfaces going DOWN and then UP.
  
  We expect bond interfaces stay UP when there is no network configuration
  change.
  
  We went though couple of options how to solve the issue and the first
  one is to add such existing patch [3] into current
  systemd-249.11-0ubuntu3.6.
  
  Could you comment whether this kind of non-security patch is likely to land 
in 22.04.1 LTS soon.
  We are able to help to bring patch into systemd package community way if you 
suggest the steps.
  
  [TESTING]
  
  Setup a jammy vm with a bond interface.
  Then:
  
  # touch /run/systemd/network/*
  # networkctl reload
  
  You can see in the logs the interfaces of the bond going up and down.
  With the fix they don't.
  
  [REGRESSION POTENTIAL]
  
  This patch modifies the behaviour of link_is_ready_to_call_set_link in
  case we have a bond interface. Therefore, things could go wrong for
  bonded interfaces.
  
  [OTHER]
  
  Fix upstream commit 9f913d37a01f71e559d099bff280.
  The fix was introduced upstream in v253.
  Jammy systemd is based on v249. Backporting is required.
  
  This patch modifies 2 functions in src/network/networkd-setlink.c:
  link_is_ready_to_call_set_link (hunk 1) and request_process_set_link (hunk 2).
  
  The way the fix is implemented is by modifing link_is_ready_to_set_link in 
the case
  the request type is SET_LINK_MASTER. In this case, it checks if the requested 
master is
  already set and if so it returns -EALREADY.
  The -EALREADY is returned to request_process_set_link which in turns cancels 
the request
  (does not go ahead to configure the link).
  
  Backport details
  Hunk 1:
  - change return type of link_is_ready_to_call_set_link from bool to int 
(since now return -EALREADY apart from 0,1).
  
  - In the original patch the check if the master is already set happens in the 
switch-case REQUEST_TYPE_SET_LINK_MASTER
  and it works fine. However, if we place the check in the equivalent place in 
jammy-systemd it causes regressions.
  For example in my setup, I have 2 interfaces in a bond, plus a third one.
  The problem I observed is that in jammy-systemd the code path (switch-case 
SET_LINK_MASTER) is also exercised by the
  third interface it returns -EALREADY and leaves it unconfigured.
  This does not seem to happen in v253.
  I guess the reason for this is that the implementation of the 'queue' that 
processes the requests has changed between v249 and v253.
  To overcome this I've restricted the check 'if master is already set' only in 
case we have a bond.
  
  Hunk 2:
  -adjust context
  
  I've run autopkgtests locally and it fails only one test, but this test
  fails even without the patch.
  
+ Test package : https://launchpad.net/~joalif/+archive/ubuntu/systemd-
+ networkd-2
+ 
+ 
  [1] https://github.com/systemd/systemd/issues/25067
  [2] Packages
  root@controlplane-001:/etc/apt0# apt list | grep -E '^(systemd/|netplan.io)'
  netplan.io/jammy-updates,now 0.105-0ubuntu2~22.04.1 amd64 
[installed,automatic]
  systemd/jammy-updates,now 249.11-0ubuntu3.6 amd64 [installed,automatic]
  [3] https://github.com/systemd/systemd/pull/25162
  [4] # lsb_release -rd
  Description:Ubuntu 22.04.1 LTS
  Release:22.04

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2003250

Title:
  networkctl reload with bond devices causes slaves to go DOWN and UP,
  causing couple of seconds of network loss

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2003250/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2003250] Re: networkctl reload with bond devices causes slaves to go DOWN and UP, causing couple of seconds of network loss

[Ioanna Alifieraki]

** Description changed:

  [SRU TEMPLATE]
  
  [DESCRIPTION]
  
  We currently use Ubuntu 22.04.1 LTS including updates for our production 
cloud (switched from legacy Centos 7).
  Although we like the distribution we recently hit serious systemd buggy 
behavior described in [1] bugreport using packages [2].
  
  Unfortunatelly the clouds we are running consist of openstack on top of
  kubernetes and we need to have complex network configuration including
  linux bond devices.
  
  Our observation is that every time we apply our configuration via CI/CD
  infrastructure using ansible and netplan (regardless whether there is
  actual network configuration change) we see approximatelly 8-16 seconds
  network interruptions and see bond interfaces going DOWN and then UP.
  
  We expect bond interfaces stay UP when there is no network configuration
  change.
  
  We went though couple of options how to solve the issue and the first
  one is to add such existing patch [3] into current
  systemd-249.11-0ubuntu3.6.
  
  Could you comment whether this kind of non-security patch is likely to land 
in 22.04.1 LTS soon.
  We are able to help to bring patch into systemd package community way if you 
suggest the steps.
  
- 
  [TESTING]
  
  Setup a jammy vm with a bond interface.
  Then:
  
  # touch /run/systemd/network/*
  # networkctl reload
  
  You can see in the logs the interfaces of the bond going up and down.
  With the fix they don't.
  
  [REGRESSION POTENTIAL]
  
+ [OTHER]
  
- [OTHER]
+ Fix upstream commit 9f913d37a01f71e559d099bff280.
+ The fix was introduced upstream in v253.
+ Jammy systemd is based on v249. Backporting is required.
+ 
+ This patch modifies 2 functions in src/network/networkd-setlink.c: 
+ link_is_ready_to_call_set_link (hunk 1) and request_process_set_link (hunk 2).
+ 
+ The way the fix is implemented is by modifing link_is_ready_to_set_link in 
the case 
+ the request type is SET_LINK_MASTER. In this case, it checks if the requested 
master is 
+ already set and if so it returns -EALREADY.
+ The -EALREADY is returned to request_process_set_link which in turns cancels 
the request
+ (does not go ahead to configure the link).
+ 
+ Backport details
+ Hunk 1: 
+ - change return type of link_is_ready_to_call_set_link from bool to int 
(since now return -EALREADY apart from 0,1).
+ 
+ - In the original patch the check if the master is already set happens in the 
switch-case REQUEST_TYPE_SET_LINK_MASTER 
+ and it works fine. However, if we place the check in the equivalent place in 
jammy-systemd it causes regressions.
+ For example in my setup, I have 2 interfaces in a bond, plus a third one.
+ The problem I observed is that in jammy-systemd the code path (switch-case 
SET_LINK_MASTER) is also exercised by the 
+ third interface it returns -EALREADY and leaves it unconfigured.
+ This does not seem to happen in v253. 
+ I guess the reason for this is that the implementation of the 'queue' that 
processes the requests has changed between v249 and v253.
+ To overcome this I've restricted the check 'if master is already set' only in 
case we have a bond.
+  
+ Hunk 2: 
+ -adjust context
+ 
+ I've run autopkgtests locally and it fails only one test, but this test
+ fails even without the patch.
+ 
  
  [1] https://github.com/systemd/systemd/issues/25067
  [2] Packages
  root@controlplane-001:/etc/apt0# apt list | grep -E '^(systemd/|netplan.io)'
  netplan.io/jammy-updates,now 0.105-0ubuntu2~22.04.1 amd64 
[installed,automatic]
  systemd/jammy-updates,now 249.11-0ubuntu3.6 amd64 [installed,automatic]
  [3] https://github.com/systemd/systemd/pull/25162
  [4] # lsb_release -rd
  Description:Ubuntu 22.04.1 LTS
  Release:22.04

** Description changed:

  [SRU TEMPLATE]
  
  [DESCRIPTION]
  
  We currently use Ubuntu 22.04.1 LTS including updates for our production 
cloud (switched from legacy Centos 7).
  Although we like the distribution we recently hit serious systemd buggy 
behavior described in [1] bugreport using packages [2].
  
  Unfortunatelly the clouds we are running consist of openstack on top of
  kubernetes and we need to have complex network configuration including
  linux bond devices.
  
  Our observation is that every time we apply our configuration via CI/CD
  infrastructure using ansible and netplan (regardless whether there is
  actual network configuration change) we see approximatelly 8-16 seconds
  network interruptions and see bond interfaces going DOWN and then UP.
  
  We expect bond interfaces stay UP when there is no network configuration
  change.
  
  We went though couple of options how to solve the issue and the first
  one is to add such existing patch [3] into current
  systemd-249.11-0ubuntu3.6.
  
  Could you comment whether this kind of non-security patch is likely to land 
in 22.04.1 LTS soon.
  We are able to help to bring patch into systemd package community way if you 
suggest the steps.
  
  [TESTING]
  
  Setup a jammy vm with a bond interface.
  

[Bug 2003250] Re: networkctl reload with bond devices causes slaves to go DOWN and UP, causing couple of seconds of network loss

[Ioanna Alifieraki]

** Description changed:

+ [SRU TEMPLATE]
+ 
+ [DESCRIPTION]
+ 
  We currently use Ubuntu 22.04.1 LTS including updates for our production 
cloud (switched from legacy Centos 7).
  Although we like the distribution we recently hit serious systemd buggy 
behavior described in [1] bugreport using packages [2].
  
  Unfortunatelly the clouds we are running consist of openstack on top of
  kubernetes and we need to have complex network configuration including
  linux bond devices.
  
  Our observation is that every time we apply our configuration via CI/CD
  infrastructure using ansible and netplan (regardless whether there is
  actual network configuration change) we see approximatelly 8-16 seconds
  network interruptions and see bond interfaces going DOWN and then UP.
  
  We expect bond interfaces stay UP when there is no network configuration
  change.
  
  We went though couple of options how to solve the issue and the first
  one is to add such existing patch [3] into current
  systemd-249.11-0ubuntu3.6.
  
  Could you comment whether this kind of non-security patch is likely to land 
in 22.04.1 LTS soon.
  We are able to help to bring patch into systemd package community way if you 
suggest the steps.
  
  
+ [TESTING]
+ 
+ Setup a jammy vm with a bond interface.
+ Then:
+ 
+ # touch /run/systemd/network/*
+ # networkctl reload
+ 
+ You can see in the logs the interfaces of the bond going up and down.
+ With the fix they don't.
+ 
+ [REGRESSION POTENTIAL]
+ 
+ 
+ [OTHER]
+ 
  [1] https://github.com/systemd/systemd/issues/25067
  [2] Packages
  root@controlplane-001:/etc/apt0# apt list | grep -E '^(systemd/|netplan.io)'
  netplan.io/jammy-updates,now 0.105-0ubuntu2~22.04.1 amd64 
[installed,automatic]
  systemd/jammy-updates,now 249.11-0ubuntu3.6 amd64 [installed,automatic]
  [3] https://github.com/systemd/systemd/pull/25162
  [4] # lsb_release -rd
  Description:Ubuntu 22.04.1 LTS
  Release:22.04

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2003250

Title:
  networkctl reload with bond devices causes slaves to go DOWN and UP,
  causing couple of seconds of network loss

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2003250/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2080062] Re: [MIR] libspelling

[Ioanna Alifieraki]

Review for Source Package: libspelling

[Summary]

The package is in pretty good state. One minor issue, a new release (0.4.1) was 
released a few days ago.
It would be nice to bump the version before promoting to main.

MIR team ACK under the constraint to resolve the below listed
required TODOs and as much as possible having a look at the
recommended TODOs.

This does not need a security review
List of specific binary packages to be promoted to main: libspelling-1-2, 
gir1.2-spelling-1, libspelling-1-doc, libspelling-1-dev, libspelling-1-dev
Specific binary packages built, but NOT to be promoted to main: 

Required TODOs:
1. Please bump the version to the latest 0.4.1

- The package has a team bug subscriber

[Rationale, Duplication and Ownership]
There is no better alternative package in main providing the same functionality.
A team (desktop-packages) is committed to own long term maintenance of this 
package.
The rationale given in the report seems valid and useful for Ubuntu.

[Dependencies]
OK:
- no other Dependencies to MIR due to this
  - libspelling checked with `check-mir`
  - all dependencies can be found in `seeded-in-ubuntu` (already in main)
  - none of the (potentially auto-generated) dependencies (Depends
and Recommends) that are present after build are not in main
- no -dev/-debug/-doc packages that need exclusion
- No dependencies in main that are only superficially tested requiring
  more tests now.

Problems: None

[Embedded sources and static linking]
OK:
- no embedded source present
- no static linking
- does not have unexpected Built-Using entries
- not a go package, no extra constraints to consider in that regard
- not a rust package, no extra constraints to consider in that regard
- Does not include vendored code

Problems: None

[Security]
OK:
- history of CVEs does not look concerning
- does not run a daemon as root
- does not use webkit1,2
- does not use lib*v8 directly
- does not parse data formats (files [images, video, audio,
  xml, json, asn.1], network packets, structures, ...) from
  an untrusted source.
- does not expose any external endpoint (port/socket/... or similar)
- does not process arbitrary web content
- does not use centralized online accounts
- does not integrate arbitrary javascript into the desktop
- does not deal with system authentication (eg, pam), etc)
- does not deal with security attestation (secure boot, tpm, signatures)
- does not deal with cryptography (en-/decryption, certificates,
  signing, ...)

Problems: None

[Common blockers]
OK:
- does not FTBFS currently
- does have a test suite that runs at build time
  - test suite fails will fail the build upon error.
- does have a non-trivial test suite that runs as autopkgtest
- This does not need special HW for build or test
- no new python2 dependency

Problems: None

[Packaging red flags]
OK:
- Ubuntu does not carry a delta
- symbols tracking is in place.
- debian/watch is present and looks ok (if needed, e.g. non-native)
- Upstream update history is good
- Debian/Ubuntu update history is good
- promoting this does not seem to cause issues for MOTUs that so far
  maintained the package
- no massive Lintian warnings
- debian/rules is rather clean
- It is not on the lto-disabled list

Problems:
- the current release is not packaged

[Upstream red flags]
OK:
- no Errors/warnings during the build
- no incautious use of malloc/sprintf (as far as we can check it)
- no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH (usage is OK inside
  tests)
- no use of user nobody
- no use of setuid / setgid
- no important open bugs (crashers, etc) in Debian or Ubuntu
- no dependency on webkit, qtwebkit or libseed
- not part of the UI for extra checks
- no translation present, but none needed for this case (user visible)?

Problems: None


** Changed in: libspelling (Ubuntu)
   Status: New => Incomplete

** Changed in: libspelling (Ubuntu)
 Assignee: Ioanna Alifieraki (joalif) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080062

Title:
  [MIR] libspelling

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libspelling/+bug/2080062/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2076381] Re: [MIR] retry

[Ioanna Alifieraki]

REVIEW FOR JAMMY:

$ rmadison retry
 retry | 1.0.4-1 | focal/universe | source, amd64, arm64, armhf, ppc64el, 
riscv64, s390x
 retry | 1.0.4-3 | jammy/universe | source, amd64, arm64, armhf, ppc64el, 
riscv64, s390x
 retry | 1.0.5-3 | noble/universe | source, amd64, arm64, armhf, ppc64el, 
riscv64, s390x
 retry | 1.0.5-3 | oracular | source, amd64, arm64, armhf, ppc64el, riscv64, 
s390x

In Jammy retry version is 1.0.4-3.
The changes between 1.0.4 and 1.0.5 are trivial(see attached diff) and do not 
change the essence of previous review.
Again no further dependencies to get in main.

MIR team ACK.

** Attachment added: "retry-diff_1-0-4_1-0-5"
   
https://bugs.launchpad.net/ubuntu/+source/retry/+bug/2076381/+attachment/5816295/+files/retry-diff_1-0-4_1-0-5

** Changed in: retry (Ubuntu Jammy)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076381

Title:
  [MIR] retry

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/retry/+bug/2076381/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2076381] Re: [MIR] retry

[Ioanna Alifieraki]

REVIEW FOR NOBLE:

$ rmadison retry
 retry | 1.0.4-1 | focal/universe | source, amd64, arm64, armhf, ppc64el, 
riscv64, s390x
 retry | 1.0.4-3 | jammy/universe | source, amd64, arm64, armhf, ppc64el, 
riscv64, s390x
 retry | 1.0.5-3 | noble/universe | source, amd64, arm64, armhf, ppc64el, 
riscv64, s390x
 retry | 1.0.5-3 | oracular   | source, amd64, arm64, armhf, ppc64el, 
riscv64, s390x

retry has the same version in both O and N.
All dependencies (lib6) already in main.

MIR team ACK.

** Changed in: retry (Ubuntu Noble)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076381

Title:
  [MIR] retry

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/retry/+bug/2076381/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2066262] Re: [MIR] libdex

[Ioanna Alifieraki]

** Changed in: libdex (Ubuntu)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066262

Title:
  [MIR] libdex

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdex/+bug/2066262/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2076381] Re: [MIR] retry

[Ioanna Alifieraki]

Review for Source Package: retry

[Summary]
Retry is a fairly small and simple package and in very good shape.
Minor problem the lack of tests during runtime.
However, since there are no tests upstream and currently retry blocks
autopkgtest, I'd suggest to have it as a recommended TODO and not block
this MIR.
The package is very small and has autopackage tests.
The same tests used in autopackage could be used at build time.


MIR team ACK
This does not need a security review
List of specific binary packages to be promoted to main: retry
Specific binary packages built, but NOT to be promoted to main: None

Recommended TODOs:
1. Add tests during build. This would be nice to go upstream first.

- The package should get a team bug subscriber before being promoted

[Rationale, Duplication and Ownership]
There is no other package in main providing the same functionality.
Foundatinos team (Ubuntu Release Managemnent Team) is committed to own long 
term maintenance of this package.
The rationale given in the report seems valid and useful for Ubuntu.


[Dependencies]
OK:
- no other Dependencies to MIR due to this
  - retry checked with `check-mir`
  - all dependencies can be found in `seeded-in-ubuntu` (already in main)
  - none of the (potentially auto-generated) dependencies (Depends
and Recommends) that are present after build are not in main
- no -dev/-debug/-doc packages that need exclusion
- No dependencies in main that are only superficially tested requiring
  more tests now.

Problems: None

[Embedded sources and static linking]
OK:
- no embedded source present
- no static linking
- does not have unexpected Built-Using entries
- not a go package, no extra constraints to consider in that regard
- not a rust package, no extra constraints to consider in that regard
- Does not include vendored code

Problems: None

[Security]
OK:
- history of CVEs does not look concerning
- does not run a daemon as root
- does not use webkit1,2
- does not use lib*v8 directly
- does not parse data formats (files [images, video, audio,
  xml, json, asn.1], network packets, structures, ...) from
  an untrusted source.
- does not expose any external endpoint (port/socket/... or similar)
- does not process arbitrary web content
- does not use centralized online accounts
- does not integrate arbitrary javascript into the desktop
- does not deal with system authentication (eg, pam), etc)
- does not deal with security attestation (secure boot, tpm, signatures)
- does not deal with cryptography (en-/decryption, certificates,
  signing, ...)

Problems: None

[Common blockers]
OK:
- does not FTBFS currently
- does have a non-trivial test suite that runs as autopkgtest
- This does not need special HW for build or test
- no new python2 dependency

Problems:
- does not have a test suite that runs at build time

[Packaging red flags]
OK:
- Ubuntu does not carry a delta
- symbols tracking not applicable for this kind of code.
- debian/watch is present and looks ok (if needed, e.g. non-native)
- Upstream update history is slow
- Debian/Ubuntu update history follows upstream
- the current release is packaged
- promoting this does not seem to cause issues for MOTUs that so far
  maintained the package
- no massive Lintian warnings
- debian/rules is rather clean
- It is not on the lto-disabled list

Problems: None

[Upstream red flags]
OK:
- no Errors/warnings during the build
- no incautious use of malloc/sprintf (as far as we can check it)
- no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH (usage is OK inside
  tests)
- no use of user nobody
- no use of setuid / setgid
- no important open bugs (crashers, etc) in Debian or Ubuntu
- no dependency on webkit, qtwebkit or libseed
- not part of the UI for extra checks
- no translation present, but none needed for this case (user visible)?

Problems: None

** Changed in: retry (Ubuntu)
   Status: New => In Progress

** Changed in: retry (Ubuntu)
 Assignee: Ioanna Alifieraki (joalif) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2076381

Title:
  [MIR] retry

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/retry/+bug/2076381/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2070882] Re: [MIR] jpeg-xl

[Ioanna Alifieraki]

Review for Source Package: jpeg-xl

[Summary]

Package looks good.
There's a bug in debian about FTBFS on riscv64 but does not affect ubuntu.

MIR team ACK under the constraint to resolve the below listed
required TODOs and as much as possible having a look at the
recommended TODOs.
This does need a security review, so I'll assign ubuntu-security

List of specific binary packages to be promoted to main: 
jpeg-xl-doc,libjxl-dev,libjxl-gdk-pixbuf,libjxl0
Specific binary packages built, but NOT to be promoted to main: 
libjpegxl-java,libjpegli-tools,libjxl-devtool,libjxl-tools

Required TODOs:
1. highway needs to be promoted before this one 
https://bugs.launchpad.net/ubuntu/+source/highway/+bug/2070807

- The package should get a team bug subscriber before being promoted

[Rationale, Duplication and Ownership]
There is no other package in main providing the same functionality.
A team (~desktop-packages) is committed to own long term maintenance of this 
package.
The rationale given in the report seems valid and useful for Ubuntu

[Dependencies]
OK:
- no -dev/-debug/-doc packages that need exclusion
- No dependencies in main that are only superficially tested requiring
  more tests now.

Problems:
- highway needed in main, currenctly under MIR 
(https://launchpad.net/bugs/2070807)


[Embedded sources and static linking]
OK:
- no embedded source present
- no static linking
- does not have unexpected Built-Using entries
- not a go package, no extra constraints to consider in that regard
- not a rust package, no extra constraints to consider in that regard
- Does not include vendored code

Problems: None

[Security]
OK:
- history of CVEs does not look concerning
- does not run a daemon as root
- does not use webkit1,2
- does not use lib*v8 directly
- does not expose any external endpoint (port/socket/... or similar)
- does not process arbitrary web content
- does not use centralized online accounts
- does not integrate arbitrary javascript into the desktop
- does not deal with system authentication (eg, pam), etc)
- does not deal with security attestation (secure boot, tpm, signatures)
- does not deal with cryptography (en-/decryption, certificates,
  signing, ...)

Problems:
- Had a few CVEs in the past
- does parse data formats (files [images, video, audio,
  xml, json, asn.1], network packets, structures, ...) from
  an untrusted source.

[Common blockers]
OK:
- does not FTBFS currently
- does have a test suite that runs at build time
  - test suite fails will fail the build upon error.
- does have a non-trivial test suite that runs as autopkgtest
- This does not need special HW for build or test
- no new python2 dependency

Problems: None

[Packaging red flags]
OK:
- Ubuntu does not carry a delta
- symbols tracking is in place.
- debian/watch is present and looks ok (if needed, e.g. non-native)
- Upstream update history is good
- Debian/Ubuntu update history is good
- the current release is packaged
- promoting this does not seem to cause issues for MOTUs that so far
  maintained the package
- no massive Lintian warnings
- debian/rules is rather clean
- It is not on the lto-disabled list

Problems: None

[Upstream red flags]
OK:
- no Errors/warnings during the build
- no incautious use of malloc/sprintf (as far as we can check it)
- no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH (usage is OK inside
  tests)
- no use of user nobody
- no use of setuid / setgid
- no important open bugs (crashers, etc) in Debian or Ubuntu
- no dependency on webkit, qtwebkit or libseed
- not part of the UI for extra checks
- no translation present, but none needed for this case

Problems:
- In debian there's a bug report that it cannot build in riscv64
  (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077336) but it builds ok 
on ubuntu.


** Bug watch added: Debian Bug tracker #1077336
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077336

** Changed in: jpeg-xl (Ubuntu)
 Assignee: Ioanna Alifieraki (joalif) => (unassigned)

** Changed in: jpeg-xl (Ubuntu)
 Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070882

Title:
  [MIR] jpeg-xl

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jpeg-xl/+bug/2070882/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2070882] Re: [MIR] jpeg-xl

[Ioanna Alifieraki]

@jbicha, I'm working on the review for this bug.

The build produces the following debs :
jpeg-xl-doc_0.10.3-4ubuntu1_all.deb
libjxl-dev_0.10.3-4ubuntu1_amd64.deb  
libjxl-gdk-pixbuf_0.10.3-4ubuntu1_amd64.deb  
libjxl0.10_0.10.3-4ubuntu1_amd64.deb

libjpegxl-java_0.10.3-4ubuntu1_amd64.deb  
libjpegli-tools_0.10.3-4ubuntu1_amd64.deb  
libjxl-devtools_0.10.3-4ubuntu1_amd64.deb
libjxl-tools_0.10.3-4ubuntu1_amd64.deb

Just a confirmation, IIUC from the description we need in main only the 
following:
jpeg-xl-doc_0.10.3-4ubuntu1_all.deb
libjxl-dev_0.10.3-4ubuntu1_amd64.deb  
libjxl-gdk-pixbuf_0.10.3-4ubuntu1_amd64.deb  
libjxl0.10_0.10.3-4ubuntu1_amd64.deb

Is this correct ?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070882

Title:
  [MIR] jpeg-xl

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jpeg-xl/+bug/2070882/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2055397] Re: netplan/systemd-networkd: route metric not applied to routes to the local subnet

[Ioanna Alifieraki]

# VERIFICATION FOCAL

 WITHOUT THE FIX

$ dpkg -l | grep systemd
ii  dbus-user-session 1.12.16-2ubuntu2.3
amd64simple interprocess messaging system (systemd --user integration)
ii  libnss-systemd:amd64  245.4-4ubuntu3.23 
amd64nss module providing dynamic user and group name resolution
ii  libpam-systemd:amd64  245.4-4ubuntu3.23 
amd64system and service manager - PAM module
ii  libsystemd0:amd64 245.4-4ubuntu3.23 
amd64systemd utility library
ii  systemd   245.4-4ubuntu3.23 
amd64system and service manager
ii  systemd-sysv  245.4-4ubuntu3.23 
amd64system and service manager - SysV links
ii  systemd-timesyncd 245.4-4ubuntu3.23 
amd64minimalistic service to synchronize local time with NTP servers

$ ip route show
default via 192.168.96.1 dev ens5 proto dhcp src 192.168.108.150 metric 100 
default via 192.168.122.1 dev enp1s0 proto dhcp src 192.168.122.192 metric 100 
default via 192.168.96.1 dev ens6 proto dhcp src 192.168.107.159 metric 200 
192.168.96.0/20 dev ens5 proto kernel scope link src 192.168.108.150 
192.168.96.0/20 dev ens6 proto kernel scope link src 192.168.107.159 
192.168.96.1 dev ens5 proto dhcp scope link src 192.168.108.150 metric 100 
192.168.96.1 dev ens6 proto dhcp scope link src 192.168.107.159 metric 200 
192.168.122.0/24 dev enp1s0 proto kernel scope link src 192.168.122.192 
192.168.122.1 dev enp1s0 proto dhcp scope link src 192.168.122.192 metric 100 

Metric does not appear on subnet

 WITH THE FIX

$ dpkg -l | grep systemd
ii  dbus-user-session 1.12.16-2ubuntu2.3
amd64simple interprocess messaging system (systemd --user integration)
ii  libnss-systemd:amd64  245.4-4ubuntu3.24 
amd64nss module providing dynamic user and group name resolution
ii  libpam-systemd:amd64  245.4-4ubuntu3.24 
amd64system and service manager - PAM module
ii  libsystemd0:amd64 245.4-4ubuntu3.24 
amd64systemd utility library
ii  systemd   245.4-4ubuntu3.24 
amd64system and service manager
ii  systemd-sysv  245.4-4ubuntu3.24 
amd64system and service manager - SysV links
ii  systemd-timesyncd 245.4-4ubuntu3.24 
amd64minimalistic service to synchronize local time with NTP servers

$ ip route show
default via 192.168.96.1 dev ens5 proto dhcp src 192.168.108.150 metric 100 
default via 192.168.122.1 dev enp1s0 proto dhcp src 192.168.122.192 metric 100 
default via 192.168.96.1 dev ens6 proto dhcp src 192.168.107.159 metric 200 
192.168.96.0/20 dev ens5 proto kernel scope link src 192.168.108.150 metric 100 
192.168.96.0/20 dev ens6 proto kernel scope link src 192.168.107.159 metric 200 
192.168.96.1 dev ens5 proto dhcp scope link src 192.168.108.150 metric 100 
192.168.96.1 dev ens6 proto dhcp scope link src 192.168.107.159 metric 200 
192.168.122.0/24 dev enp1s0 proto kernel scope link src 192.168.122.192 metric 
100 
192.168.122.1 dev enp1s0 proto dhcp scope link src 192.168.122.192 metric 100 

Metric does apprear on subnet

** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055397

Title:
  netplan/systemd-networkd: route metric not applied to routes to the
  local subnet

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2055397/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2066262] Re: [MIR] libdex

[Ioanna Alifieraki]

Review for Source Package: libdex

[Summary]
MIR team ACK under the constraint to resolve the below listed
required TODOs and as much as possible having a look at the
recommended TODOs.
This does need a security review, so I'll assign ubuntu-security
List of specific binary packages to be promoted to main: gir1.2-dex-1, 
libdex-1-1, libdex-dev, libdex-doc
Specific binary packages built, but NOT to be promoted to main: 

Notes:

Overall the package is in pretty good shape.
The only problem is the absence of autpkg tests.
However, the desktop team has worked around it, and has provided plans
to test libdex in the context of sysprof :
https://wiki.ubuntu.com/DesktopTeam/TestPlans/Sysprof
https://wiki.ubuntu.com/DesktopTeam/TestPlans/GnomeBuilder

The current release is not packaged, the bug was opened before the latest 
release was
released, and I guess it is in your plans to bump the version.

With regards to @jbicha's concern on io_uring security, IMO this is mainly 
kernel's/liburing
problem, but I agree that security could have a look to rule out any sideffects 
in this pacakge.

Required TODOs:
1. Please bump to the latest upstream version
2. The package should get a team bug subscriber before being promoted

[Rationale, Duplication and Ownership]
There is no better alternative package in main providing the same functionality.
A team (~desktop-packages) is committed to own long term maintenance of this 
package.
The rationale given in the report seems valid and useful for Ubuntu

[Dependencies]
OK:
- no other Dependencies to MIR due to this
  - libdex checked with `check-mir`
  - all dependencies can be found in `seeded-in-ubuntu` (already in main)
  - none of the (potentially auto-generated) dependencies (Depends
and Recommends) that are present after build are not in main
- no -dev/-debug/-doc packages that need exclusion
- No dependencies in main that are only superficially tested requiring
  more tests now.

Problems: None

[Embedded sources and static linking]
OK:
- no embedded source present
- no static linking
- does not have unexpected Built-Using entries
- not a go package, no extra constraints to consider in that regard
- not a rust package, no extra constraints to consider in that regard
- Does not include vendored code

Problems: None

[Security]
OK:
- history of CVEs does not look concerning
- does not run a daemon as root
- does not use webkit1,2
- does not use lib*v8 directly
- does not parse data formats (files [images, video, audio,
  xml, json, asn.1], network packets, structures, ...) from
  an untrusted source.
- does not expose any external endpoint (port/socket/... or similar)
- does not process arbitrary web content
- does not use centralized online accounts
- does not integrate arbitrary javascript into the desktop
- does not deal with system authentication (eg, pam), etc)
- does not deal with security attestation (secure boot, tpm, signatures)
- does not deal with cryptography (en-/decryption, certificates,

Problems: None

[Common blockers]
OK:
- does not FTBFS currently
- does have a test suite that runs at build time
  - test suite fails will fail the build upon error.
- This does not need special HW for build or test
- a non-trivial test on this level does not make sense (the lib alone
  is only doing rather simple things),  the overall solution (app+libs)
  is tested accodring to 
  https://wiki.ubuntu.com/DesktopTeam/TestPlans/Sysprof and
  https://wiki.ubuntu.com/DesktopTeam/TestPlans/GnomeBuilder
- no new python2 dependency

Problems:
- does not have a non-trivial test suite that runs as autopkgtest

[Packaging red flags]
OK:
- Ubuntu does not carry a delta
- symbols tracking is in place.
- debian/watch is present and looks ok (if needed, e.g. non-native)
- Upstream update history is good
- Debian/Ubuntu update history is good
- the current release is packaged
- promoting this does not seem to cause issues for MOTUs that so far
  maintained the package
- no massive Lintian warnings
- debian/rules is rather clean
- It is not on the lto-disabled list

Problems:
- the current release is not packaged

[Upstream red flags]
OK:
- no Errors/warnings during the build
- no incautious use of malloc/sprintf (as far as we can check it)
- no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH (usage is OK inside
  tests)
- no use of user nobody
- no use of setuid / setgid
- no important open bugs (crashers, etc) in Debian or Ubuntu
- no dependency on webkit, qtwebkit or libseed
- not part of the UI for extra checks
- no translation present, but none needed for this case (user visible)?

Problems: None


** Changed in: libdex (Ubuntu)
 Assignee: Ioanna Alifieraki (joalif) => (unassigned)

** Changed in: libdex (Ubuntu)
 Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066262

Title:
  [M

[Bug 2055397] Re: netplan/systemd-networkd: route metric not applied to routes to the local subnet

[Ioanna Alifieraki]

** Description changed:

+ [SRU TEMPLATE]
+ 
+ [DESCRIPTION]
+ 
  Cloud-init introduced a feature to configure policy routing on AWS EC2 
instances with multiple NICs in
  
https://github.com/canonical/cloud-init/commit/0ca5f31043e2d98eab31a43d9dde9bdaef1435cb
 targeting v24.1.
  
  Cloud-init generates the following netplan config:
  
  ```
  $ cat /etc/netplan/50-cloud-init.yaml
  network:
- ethernets:
- ens5:
- dhcp4: true
- dhcp4-overrides: &id001
- route-metric: 100
- dhcp6: true
- dhcp6-overrides: *id001
- match:
- macaddress: 0a:c8:ab:90:c2:fb
- set-name: ens5
- ens6:
- dhcp4: true
- dhcp4-overrides:
- route-metric: 200
- use-routes: true
- dhcp6: false
- match:
- macaddress: 0a:c6:55:a1:dc:3b
- routes:
- -   table: 101
- to: 0.0.0.0/0
- via: 192.168.0.1
- -   table: 101
- to: 192.168.0.0/20
- routing-policy:
- -   from: 192.168.10.212
- table: 101
- set-name: ens6
- version: 2
+ ethernets:
+ ens5:
+ dhcp4: true
+ dhcp4-overrides: &id001
+ route-metric: 100
+ dhcp6: true
+ dhcp6-overrides: *id001
+ match:
+ macaddress: 0a:c8:ab:90:c2:fb
+ set-name: ens5
+ ens6:
+ dhcp4: true
+ dhcp4-overrides:
+ route-metric: 200
+ use-routes: true
+ dhcp6: false
+ match:
+ macaddress: 0a:c6:55:a1:dc:3b
+ routes:
+ -   table: 101
+ to: 0.0.0.0/0
+ via: 192.168.0.1
+ -   table: 101
+ to: 192.168.0.0/20
+ routing-policy:
+ -   from: 192.168.10.212
+ table: 101
+ set-name: ens6
+ version: 2
  ```
  
  Which renders the following systemd-networkd config files:
  
  ```
  $ cat 10-netplan-ens5.link
  [Match]
  MACAddress=0a:c8:ab:90:c2:fb
  
  [Link]
  Name=ens5
  WakeOnLan=off
  
- 
  $ cat 10-netplan-ens5.network
  [Match]
  MACAddress=0a:c8:ab:90:c2:fb
  Name=ens5
  
  [Network]
  DHCP=yes
  LinkLocalAddressing=ipv6
  
  [DHCP]
  RouteMetric=100
  UseMTU=true
  
- 
  $ cat 10-netplan-ens6.link
  [Match]
  MACAddress=0a:c6:55:a1:dc:3b
  
  [Link]
  Name=ens6
  WakeOnLan=off
- 
  
  $ cat 10-netplan-ens6.network
  [Match]
  MACAddress=0a:c6:55:a1:dc:3b
  Name=ens6
  
  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6
  
  [Route]
  Destination=0.0.0.0/0
  Gateway=192.168.0.1
  Table=101
  
  [Route]
  Destination=192.168.0.0/20
  Scope=link
  Table=101
  
  [RoutingPolicyRule]
  From=192.168.10.212
  Table=101
  
  [DHCP]
  RouteMetric=200
  UseMTU=true
  ```
  
  Which configures the instance with the following state in Ubuntu Focal:
  
  ```
  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
- link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
- inet 127.0.0.1/8 scope host lo
-valid_lft forever preferred_lft forever
- inet6 ::1/128 scope host
-valid_lft forever preferred_lft forever
+ link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ inet 127.0.0.1/8 scope host lo
+    valid_lft forever preferred_lft forever
+ inet6 ::1/128 scope host
+    valid_lft forever preferred_lft forever
  2: ens5:  mtu 9001 qdisc mq state UP group 
default qlen 1000
- link/ether 0a:c8:ab:90:c2:fb brd ff:ff:ff:ff:ff:ff
- inet 192.168.12.94/20 brd 192.168.15.255 scope global dynamic ens5
-valid_lft 2087sec preferred_lft 2087sec
- inet6 2a05:d012:ea0:c500:6d12:2b20:5fef:a502/128 scope global dynamic 
noprefixroute
-valid_lft 440sec preferred_lft 130sec
- inet6 fe80::8c8:abff:fe90:c2fb/64 scope link
-valid_lft forever preferred_lft forever
+ link/ether 0a:c8:ab:90:c2:fb brd ff:ff:ff:ff:ff:ff
+ inet 192.168.12.94/20 brd 192.168.15.255 scope global dynamic ens5
+    valid_lft 2087sec preferred_lft 2087sec
+ inet6 2a05:d012:ea0:c500:6d12:2b20:5fef:a502/128 scope global dynamic 
noprefixroute
+    valid_lft 440sec preferred_lft 130sec
+ inet6 fe80::8c8:abff:fe90:c2fb/64 scope link
+    valid_lft forever preferred_lft forever
  3: ens6:  mtu 9001 qdisc mq state UP group 
default qlen 1000
- link/ether 0a:c6:55:a1:dc:3b brd ff:ff:ff:ff:ff:ff
- inet 192.168.10.212/20 brd 192.168.15.255 scope global dynamic ens6
-valid_lft 2083sec preferred_lft 2083sec
- inet6 fe80::8c6:55ff:fea1:dc3b/64 scope link
-valid_lft forever preferred_lft forever
- 
+ link/ether 0a:c6:55:a1:dc:3b brd ff:ff:ff:ff:ff:ff
+ inet 192.168.10.212/20 brd 192.168.15.255 scope global dynamic en

[Bug 2056099] Re: [MIR] tree

[Ioanna Alifieraki]

Review for Source Package: tree

[Summary]
This is mature software and the pacakge is in pretty good state.
They only problem is missing tests at build time.
MIR team ACK under the constraint to resolve the below listed
required TODOs and as much as possible having a look at the
recommended TODOs.
This does not need a security review
List of specific binary packages to be promoted to main: tree
Specific binary packages built, but NOT to be promoted to main: 

Notes:
Required TODOs:
1. There are no tests running at build time. Could you please add some ?
   This could be the same tests with autopackage test, but running at build 
time,
   and fail the build in case of an error.


- The package should get a team bug subscriber before being promoted

[Rationale, Duplication and Ownership]
There are other packages in main providing the same functionality, however tree 
is better
and makes sense to have it in main.
Foundations team is committed to own long term maintenance of this package.
The rationale given in the report seems valid and useful for Ubuntu

[Dependencies]
OK:
- no other Dependencies to MIR due to this
 - SRCPKG checked with `check-mir`
 - all dependencies can be found in `seeded-in-ubuntu` (already in main)
 - none of the (potentially auto-generated) dependencies (Depends
   and Recommends) that are present after build are not in main
- no -dev/-debug/-doc packages that need exclusion
- No dependencies in main that are only superficially tested requiring
  more tests now.

Problems: None

[Embedded sources and static linking]
OK:
- no embedded source present
- no static linking
- does not have unexpected Built-Using entries
- not a go package, no extra constraints to consider in that regard
- not a rust package, no extra constraints to consider in that regard

Problems: None

[Security]
OK:
- history of CVEs does not look concerning
- does not run a daemon as root
- does not use webkit1,2
- does not use lib*v8 directly
- does not parse data formats (files [images, video, audio,
  xml, json, asn.1], network packets, structures, ...) from
  an untrusted source.
- does not expose any external endpoint (port/socket/... or similar)
- does not process arbitrary web content
- does not use centralized online accounts
- does not integrate arbitrary javascript into the desktop
- does not deal with system authentication (eg, pam), etc)
- does not deal with security attestation (secure boot, tpm, signatures)
- does not deal with cryptography (en-/decryption, certificates,
  signing, ...)

Problems: None

[Common blockers]
OK:
- does not FTBFS currently
- does have a non-trivial test suite that runs as autopkgtest
- This does not need special HW for build or test
- no new python2 dependency

Problems:
- does not have a test suite that runs at build time

[Packaging red flags]
OK:
- Ubuntu does not carry a delta
- symbols tracking not applicable for this kind of code.
- debian/watch is present and looks ok (if needed, e.g. non-native)
- Upstream update history is good
- Debian/Ubuntu update history is good
- the current release is packaged
- promoting this does not seem to cause issues for MOTUs that so far
  maintained the package
- no massive Lintian warnings
- debian/rules is rather clean
- It is not on the lto-disabled list

Problems: None

[Upstream red flags]
OK:
- no Errors/warnings during the build
- no incautious use of malloc/sprintf (as far as we can check it)
- no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH (usage is OK inside
  tests)
- no use of user nobody
- no use of setuid / setgid
- no important open bugs (crashers, etc) in Debian or Ubuntu
- no dependency on webkit, qtwebkit, seed or libgoa-*
- not part of the UI for extra checks
- no translation present, but none needed for this case

Problems: None


** Changed in: tree (Ubuntu)
   Status: New => Incomplete

** Changed in: tree (Ubuntu)
 Assignee: Ioanna Alifieraki (joalif) => (unassigned)

** Changed in: tree (Ubuntu)
 Assignee: (unassigned) => Alexandre Esse (ahresse)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056099

Title:
  [MIR] tree

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tree/+bug/2056099/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2055434] Re: [MIR] pemmican

[Ioanna Alifieraki]

Review for Source Package: pemmican

[Summary]

This is a small utility that warns users of issues with power supply on 
Raspberry Pi 5 platforms.
It runs 3 utilities (pemmican-cli, pemmican-mon and pemmican-reset) as root and 
therefore 
I believe a sec review is due.


MIR team ACK under the constraint to resolve the below listed
required TODOs and as much as possible having a look at the
recommended TODOs.
This does need a security review, so I'll assign ubuntu-security
List of specific binary packages to be promoted to main: pemmican-common, 
pemmican-desktop, pemmican-doc, pemmican-server
Specific binary packages built, but NOT to be promoted to main: 

Notes:
Recommended TODOs:
1. The url you're link for more information 
(https://github.com/waveform80/pemmican/blob/main/pemmican/const.py#L20) 
returns 404, you may want to change it.

- The package should get a team bug subscriber before being promoted

[Rationale, Duplication and Ownership]
There is no other package in main providing the same functionality.
A team is committed to own long term maintenance of this package (foundations).
The rationale given in the report seems valid and useful for Ubuntu

[Dependencies]
OK:
- no other Dependencies to MIR due to this
- no -dev/-debug/-doc packages that need exclusion
- No dependencies in main that are only superficially tested requiring
  more tests now.

Problems: None

[Embedded sources and static linking]
OK:
- no embedded source present
- no static linking
- does not have unexpected Built-Using entries
- not a go package, no extra constraints to consider in that regard
- not a rust package, no extra constraints to consider in that regard
- Does not include vendored code

Problems: None

[Security]
OK:
- history of CVEs does not look concerning
- does not use webkit1,2
- does not use lib*v8 directly
- does not parse data formats (files [images, video, audio,
  xml, json, asn.1], network packets, structures, ...) from
  an untrusted source.
- does not expose any external endpoint (port/socket/... or similar)
- does not process arbitrary web content
- does not use centralized online accounts
- does not integrate arbitrary javascript into the desktop
- does not deal with system authentication (eg, pam), etc)
- does not deal with security attestation (secure boot, tpm, signatures)
- does not deal with cryptography (en-/decryption, certificates,
  signing, ...)

Problems:
- does run a daemon as root

[Common blockers]
OK:
- does not FTBFS currently
- does have a test suite that runs at build time
  - test suite fails will fail the build upon error.
- does have a non-trivial test suite that runs as autopkgtest
- no new python2 dependency
- Python package, but using dh_python

Problems: None

[Packaging red flags]
OK:
- Ubuntu does carry a delta, but it is reasonable and maintenance under
  control
- symbols tracking not applicable for this kind of code.
- debian/watch is present and looks ok (if needed, e.g. non-native)
- Upstream update history is good
- Debian/Ubuntu update history is good
- the current release is packaged
- promoting this does not seem to cause issues for MOTUs that so far
  maintained the package
- no massive Lintian warnings
- debian/rules is rather clean
- It is not on the lto-disabled list

Problems: None

[Upstream red flags]
OK:
- no Errors/warnings during the build
- no incautious use of malloc/sprintf (the language has no direct MM)
- no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH (usage is OK inside
  tests)
- no use of user nobody
- no use of setuid / setgid
- no important open bugs (crashers, etc) in Debian or Ubuntu
- no dependency on webkit, qtwebkit, seed or libgoa-*
- not part of the UI for extra checks
- translation present

Problems: None


** Changed in: pemmican (Ubuntu)
   Status: New => Confirmed

** Changed in: pemmican (Ubuntu)
     Assignee: Ioanna Alifieraki (joalif) => (unassigned)

** Changed in: pemmican (Ubuntu)
 Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055434

Title:
  [MIR] pemmican

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pemmican/+bug/2055434/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2048781] Re: [MIR] authd

[Ioanna Alifieraki]

@jibel

> can you point to the Debian Go packaging guidelines you're mentioning?
https://go-team.pages.debian.net/packaging.html

It is stated in the bug description:
"- This package violates Debian Policy. It vendorizes various Go (in vendor/) 
and Rust libraries (in vendor_rust/). We are maintaining them up to date with 
dependabot in our upstream CI. The Go part is covered by the govulncheck 
security scanning on the Go version we are depending on and its vendored 
dependency."

However there's no TODO wrt to that. Just the translations as a
recommendation.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2048781

Title:
  [MIR] authd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/authd/+bug/2048781/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2051850] Re: [MIR] trace-cmd

[Ioanna Alifieraki]

Review for Source Package: trace-cmd

[Summary]
MIR team ACK under the constraint to resolve the below listed
required TODOs and as much as possible having a look at the
recommended TODOs.

Although the package can pass our security check-list, trace-cmd itself runs as 
root
to setup events in ftrace kernel subsystem.
This combined with the use of setuid/setgid in trace-record.c (change_user()) 
and
extensive use of malloc/sprintf, I think are good enough reasons for a sec 
review.

This does need a security review, so I'll assign ubuntu-security, after the 
required TODOs 
are addressed.

List of specific binary packages to be promoted to main: trace-cmd, 
libtracecmd1,libtracecmd-dev
Specific binary packages built, but NOT to be promoted to main:

Notes:
Required TODOs:
1. Other dependies to MIR:
   a. libtracefs - 
https://bugs.launchpad.net/ubuntu/+source/libtracefs/+bug/2051925
   b. libtraceevent - 
https://bugs.launchpad.net/ubuntu/+source/libtraceevent/+bug/2051916
2. No tests during build, please add tests.
3. No autopackage tests present. This TODO incorporates Christain's feedback 
(comment #2)
   "but on this level we should require to set up some good autopkgtests that 
help us to 
ensure this full stack is really working well on e.g. changed kernels."
Please add autopackage tests.

Recommended TODOs:
4. The output of 'lintian --pendatic --tag-display-limit 0' yields many warnings
   some of them segfaults. Not sure if this is a problem of the package or troff
   but please take a look. (https://pastebin.ubuntu.com/p/JYGrJ7wnJz/)
5. There a few warning (unused return values) during build
6. The package should get a team bug subscriber before being promoted

[Rationale, Duplication and Ownership]
There is no other package in main providing the same functionality.
Foundations team is committed to own long term maintenance of this package.
The rationale given in the report seems valid and useful for Ubuntu

[Dependencies]
OK:
- no -dev/-debug/-doc packages that need exclusion
- No dependencies in main that are only superficially tested requiring
  more tests now.

Problems:
- other Dependencies to MIR due to this

[Embedded sources and static linking]
OK:
- no embedded source present
-  no static linking
- does not have unexpected Built-Using entries
OK:
- not a go package, no extra constraints to consider in that regard
- not a rust package, no extra constraints to consider in that regard

Problems: None

[Security]
OK:
- history of CVEs does not look concerning
- does not run a deamon as root
- does not use webkit1,2
- does not use lib*v8 directly
- does not parse data formats (files [images, video, audio,
  xml, json, asn.1], network packets, structures, ...) from
  an untrusted source.
- does not expose any external endpoint (port/socket/... or similar)
- does not process arbitrary web content
- does not use centralized online accounts
- does not integrate arbitrary javascript into the desktop
- does not deal with system authentication (eg, pam), etc)
- does not deal with security attestation (secure boot, tpm, signatures)
- does not deal with cryptography (en-/decryption, certificates,
  signing, ...)

Problems:
- this does not  make appropriate (for its exposure) use of established risk
  mitigation features (dropping permissions, using temporary environments,
  restricted users/groups, seccomp, systemd isolation features,
  apparmor, ...)

[Common blockers]
OK:
- does not FTBFS currently
- This does not need special HW for build or test
- no new python2 dependency

Problems:
- does not have a test suite that runs at build time
- does not have a non-trivial test suite that runs as autopkgtest

[Packaging red flags]
OK:
- Ubuntu does not carry a delta
- symbols tracking is in place.
- debian/watch is present and looks ok (if needed, e.g. non-native)
- Upstream update history is good
- Debian/Ubuntu update history is slow
- the current release is packaged
- promoting this does not seem to cause issues for MOTUs that so far
  maintained the package
- debian/rules is rather clean
- It is not on the lto-disabled list

Problems:
- massive Lintian warnings - https://pastebin.ubuntu.com/p/JYGrJ7wnJz/

[Upstream red flags]
OK:
- no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH (usage is OK inside
  tests)
- no important open bugs (crashers, etc) in Debian or Ubuntu
- no dependency on webkit, qtwebkit, seed or libgoa-*
- not part of the UI for extra checks
- no translation present, but none needed for this case (user visible)?

Problems:
- a few warnings during the build about ignoring return values
- heavy use of malloc and sprintf
- use of setuid/setgid

** Changed in: trace-cmd (Ubuntu)
   Status: New => Incomplete

** Changed in: trace-cmd (Ubuntu)
 Assignee: Ioanna Alifieraki (joalif) => (unassigned)

** Changed in: trace-cmd (Ubuntu)
 Assignee: (unassigned) => Paul Mars (upils)

-- 
You received this bug notification because yo

[Bug 2052822] Re: [MIR] langtable

[Ioanna Alifieraki]

Review for Source Package: langtabtle

[Summary]
MIR team ACK
This does not need a security review
List of specific binary packages to be promoted to main: python3-langtable
Specific binary packages built, but NOT to be promoted to main: 

Notes:
- The package should get a team bug subscriber before being promoted

[Rationale, Duplication and Ownership]
There is no other package in main providing the same functionality.
A team is committed to own long term maintenance of this package.
The rationale given in the report seems valid and useful for Ubuntu

[Dependencies]
OK:
- no other Dependencies to MIR due to this
- no -dev/-debug/-doc packages that need exclusion
- No dependencies in main that are only superficially tested requiring
  more tests now.

Problems: None

[Embedded sources and static linking]
OK:
- no embedded source present
- no static linking
- does not have unexpected Built-Using entries
- not a go package, no extra constraints to consider in that regard
- not a rust package, no extra constraints to consider in that regard
- Does not include vendored code

Problems: None

[Security]
OK:
- history of CVEs does not look concerning
- does not run a daemon as root
- does not use webkit1,2
- does not use lib*v8 directly
- does not parse data formats (files [images, video, audio,
  xml, json, asn.1], network packets, structures, ...) from
  an untrusted source.
- does not expose any external endpoint (port/socket/... or similar)
- does not process arbitrary web content
- does not use centralized online accounts
- does not integrate arbitrary javascript into the desktop
- does not deal with system authentication (eg, pam), etc)
- does not deal with security attestation (secure boot, tpm, signatures)
- does not deal with cryptography (en-/decryption, certificates,
  signing, ...)

Problems: None

[Common blockers]
OK:
- does not FTBFS currently
- does have a test suite that runs at build time
  - test suite fails will fail the build upon error.
- does have a non-trivial test suite that runs as autopkgtest
- This does not need special HW for build or test
- no new python2 dependency
- Python package, but using dh_python

Problems: None

[Packaging red flags]
OK:
- Ubuntu does not carry a delta
- symbols tracking not applicable for this kind of code.
- debian/watch is present and looks ok (if needed, e.g. non-native)
- Upstream update history is good
- Debian/Ubuntu update history is good
- the current release is packaged
- promoting this does not seem to cause issues for MOTUs that so far
  maintained the package
- no massive Lintian warnings
- debian/rules is rather clean
- It is not on the lto-disabled list

Problems: None

[Upstream red flags]
OK:
- no Errors/warnings during the build
- no incautious use of malloc/sprintf (the language has no direct MM)
- no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH (usage is OK inside
  tests)
- no use of user nobody
- no use of setuid / setgid
- no important open bugs (crashers, etc) in Debian or Ubuntu
- no dependency on webkit, qtwebkit, seed or libgoa-*
- not part of the UI for extra checks
- no translation present, but none needed for this case (user visible)?

Problems: None


** Changed in: langtable (Ubuntu)
   Status: New => In Progress

** Changed in: langtable (Ubuntu)
 Assignee: Ioanna Alifieraki (joalif) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2052822

Title:
  [MIR] langtable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/langtable/+bug/2052822/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1975523] Re: [MIR] Promote to main in Jammy and Kinetic

[Ioanna Alifieraki]

Review for Package: ruby-webrick

[Summary]
WEBrick is an HTTP server toolkit that can be configured as an HTTPS server, 
a proxy server and a virtual-host server.
It used to be provided with the standard library of the Ruby interpreter, and 
has 
been available as a standalone gem since ruby3.0.

MIR team ACK
This does need a security review, so I'll assign ubuntu-security
List of specific binary packages to be promoted to main: ruby-webrick

Notes:
- The package should get a team bug subscriber before being promoted


[Duplication]
There is no other package in main providing the same functionality.

[Dependencies]
OK:
- no other Dependencies to MIR due to this
   - checked with check-mir
   - not listed in seeded-in-ubuntu
   - none of the (potentially auto-generated) dependencies (Depends
 and Recommends) that are present after build are not in main
- no -dev/-debug/-doc packages that need exclusion
- No dependencies in main that are only superficially tested requiring
   more tests now.

Problems: None

[Embedded sources and static linking]
OK:
- no embedded source present
- no static linking
- does not have odd Built-Using entries
- not a go package, no extra constraints to consider in that regard
- No vendoring used, all Built-Using are in main

Problems: None

[Security]
OK:
- history of CVEs does not look concerning
- does not run a daemon as root
- does not use webkit1,2
- does not use lib*v8 directly
- does not process arbitrary web content
- does not use centralized online accounts
- does not integrate arbitrary javascript into the desktop
- does not deal with system authentication (eg, pam), etc)
- does not deal with security attestation (secure boot, tpm, signatures)

Problems:
- does open a port/socket
- does not parse data formats

[Common blockers]
OK:
- does not FTBFS currently
- does have a test suite that runs at build time
   - test suite fails will fail the build upon error.
- does have a non-trivial test suite that runs as autopkgtest
- no new python2 dependency

Problems: None

[Packaging red flags]
OK:
- Ubuntu does carry a delta, but it is reasonable and maintenance under
  control (only one patch which is backported from upstream and will be
  removed eventually)
- symbols tracking not applicable for this kind of code.
- d/watch is present and looks ok (if needed, e.g. non-native)
- Upstream update history is good
- Debian/Ubuntu update history is slow
- the current release is packaged
- promoting this does not seem to cause issues for MOTUs that so far
  maintained the package
- no massive Lintian warnings
- d/rules is rather clean
- It is not on the lto-disabled list

Problems: None

[Upstream red flags]

OK:
TODO: - no Errors/warnings during the build
- no incautious use of malloc/sprintf (as far as we can check it)
- no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH (usage is OK inside
  tests)
- no use of user nobody
- use of setuid, but ok. The package provides an su(user) function in 
lib/webrick/utils.rb
  which makes use of setuid and setgid to change uid and gid of the process to 
the ones of the
  user. However this function is used to drop priviledges in case WEBrick is 
started as one user
  to gain permission to bind to port 80 or 443 (see lib/webrick.rb).
- no important open bugs (crashers, etc) in Debian or Ubuntu
- no dependency on webkit, qtwebkit, seed or libgoa-*
- not part of the UI for extra checks
- no translation present, but none needed for this case 

Problems: None

** Changed in: ruby-webrick (Ubuntu Kinetic)
 Assignee: Ioanna Alifieraki (joalif) => (unassigned)

** Changed in: ruby-webrick (Ubuntu Kinetic)
 Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975523

Title:
  [MIR] Promote to main in Jammy and Kinetic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ruby-webrick/+bug/1975523/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1975736] Re: stateful snapshot not working

[Ioanna Alifieraki]

@Stephane, thank you for reply, I'll do what you suggest and I'll open
an issue in github (if I confirm this is a bug)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975736

Title:
  stateful snapshot not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1975736/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1975736] Re: stateful snapshot not working

[Ioanna Alifieraki]

Some initial analysis I've done.

The error "Error: Migration is disabled when VirtFS export path 
'/var/lib/lxd/devices/f-vm/config.mount' is mounted in the guest using 
mount_tag 'config'" comes from qemu.
IIUC qemu returns this error because 9p driver is in use 
(see 
https://gitlab.com/qemu-project/qemu/-/commit/e9a0152ba182c5ce9929ee60f83a37b61a1d5195
 ).

In lxd logs I can see :
"WARNING[2022-05-25T17:14:46Z] Unable to use virtio-fs for config drive, using 
9p as a fallback  err="Stateful migration unsupported" instance=f-vm 
instanceType=virtual-machine project=default".

This warning comes from [1] because DiskVMVirtiofsdStart returns error [2].
IIUC DiskVMVirtiofsdStart returns error  because stateful.migration is set to 
true and according to [3], 
"To allow for this, the VM must have migration.stateful set to true and 
size.state set on its root disk device to allow 
for additional space to store the runtime state. In this mode, PCI passthrough 
will be disabled as will be virtiofs."
However, when falling back to 9p also does not support stateful migration.


[1] 
https://github.com/lxc/lxd/blob/master/lxd/instance/drivers/driver_qemu.go#L1198
[2] 
https://github.com/lxc/lxd/blob/837d8228b45010bcbeecf581720e2ce7f17f04dc/lxd/device/device_utils_disk.go#L447
[3] 
https://discuss.linuxcontainers.org/t/lxd-4-12-has-been-released/10424#stateful-stop-and-stateful-snapshots-for-virtual-machines-4

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975736

Title:
  stateful snapshot not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1975736/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1975736] [NEW] stateful snapshot not working

[Ioanna Alifieraki]

Public bug reported:

lxc snapshot --stateful fails with 
"Error: Migration is disabled when VirtFS export path 
'/var/lib/lxd/devices/f-vm/config.mount' is mounted in the guest using 
mount_tag 'config'"

Reproducer:
$ lxc profile show default
config:
  limits.memory: 4096MiB
  migration.stateful: "true"
description: Default LXD profile
devices:
  eth0:
name: eth0
network: lxdbr0
type: nic
  root:
path: /
pool: default
size.state: 4096MiB
type: disk
name: default
used_by: []

$ lxc launch ubuntu:focal f-vm --vm
$ lxc snapshot --stateful f-vm
Error: Migration is disabled when VirtFS export path 
'/var/lib/lxd/devices/f-vm/config.mount' is mounted in the guest using 
mount_tag 'config'


Versions affected: 4.24, 5.0, latest upstream (at commit 
837d8228b45010bcbeecf581720e2ce7f17f04dc)

** Affects: lxd (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1975736

Title:
  stateful snapshot not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1975736/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971767] Re: [MIR] libfreeaptx

[Ioanna Alifieraki]

Review for Package: libfreeaptx

[Summary]
libfreeaptx is a small library and is Open Source implementation of Audio 
Processing Technology codec (aptX)
derived from ffmpeg 4.0 project and licensed under LGPLv2.1+. This codec is 
mainly used in Bluetooth A2DP profile.
It provides dynamic linked shared library libfreeaptx.so and simple command 
line utilities for encoding and decoding operations.
libfreeaptx is based on version 0.2.0 of libopenaptx with the intent of 
continuing under a free license without the additional 
license restriction added to libopenaptx 0.2.1.
Binary packages from source package :
libfreeaptx-dev: provides development files
freeaptx-utils: provides utilities for encoding and decoding (freeaptxenc, 
freeaptxdec)
libfreeaptx0: provides the shared library

MIR team ACK.

This does need a security review, so I'll assign ubuntu-security.

List of specific binary packages to be promoted to main: libfreeaptx0,
freeaptx-utils, libfreeaptx-dev


Notes:
Recommended TODOs:
- The package should get a team bug subscriber before being promoted
- Although it is explained why there are no tests in the package and the team
  commits to manually test it, it would still be nice to have some tests either 
  at build time or autopackage if possible (this is only recommended).

[Duplication]
There is no other package in main providing the same functionality.

[Dependencies]
OK:
- no other Dependencies to MIR due to this
   - checked with check-mir
   - not listed in seeded-in-ubuntu
   - none of the (potentially auto-generated) dependencies (Depends
 and Recommends) that are present after build are not in main
- no -dev/-debug/-doc packages that need exclusion
- No dependencies in main that are only superficially tested requiring
  more tests now.

Problems: None

[Embedded sources and static linking]
OK:
- no embedded source present
- no static linking
- does not have odd Built-Using entries
- not a go package, no extra constraints to consider in that regard
- No vendoring used, all Built-Using are in main

Problems: None

[Security]
OK:
- history of CVEs does not look concerning
- does not run a daemon as root
- does not use webkit1,2
- does not use lib*v8 directly
- does not open a port/socket
- does not process arbitrary web content
- does not use centralized online accounts
- does not integrate arbitrary javascript into the desktop
- does not deal with system authentication (eg, pam), etc)
- does not deal with security attestation (secure boot, tpm, signatures)

Problems:
- does parse data formats


[Common blockers]
OK:
- does not FTBFS currently
- the package does not provide any tests at all. The subscribed team commits to 
manually
  test the package as described in bug description (section [Quality assurance 
- testing])
- no new python2 dependency


Problems: None

[Packaging red flags]
OK:
- Ubuntu does not carry a delta
- symbols tracking is in place
- d/watch is present and looks ok (if needed, e.g. non-native)
- Upstream update history is sporadic
- Debian/Ubuntu update history is sporadic
- the current release is packaged
- promoting this does not seem to cause issues for MOTUs that so far
  maintained the package
- no massive Lintian warnings
- d/rules is rather clean
- It is not on the lto-disabled list

Problems: None


[Upstream red flags]
OK:
- no Errors/warnings during the build
- no incautious use of malloc/sprintf (as far as we can check it)
- no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH (usage is OK inside
  tests)
- no use of user nobody
- no use of setuid
- no important open bugs (crashers, etc) in Debian or Ubuntu
- no dependency on webkit, qtwebkit, seed or libgoa-*
- not part of the UI for extra checks
- no translation present, but none needed for this case

Problems: None

** Changed in: libfreeaptx (Ubuntu)
 Assignee: Ioanna Alifieraki (joalif) => (unassigned)

** Changed in: libfreeaptx (Ubuntu)
 Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971767

Title:
  [MIR] libfreeaptx

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libfreeaptx/+bug/1971767/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971767] Re: [MIR] libfreeaptx

[Ioanna Alifieraki]

** Changed in: libfreeaptx (Ubuntu)
 Assignee: (unassigned) => Ioanna Alifieraki (joalif)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971767

Title:
  [MIR] libfreeaptx

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libfreeaptx/+bug/1971767/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1965115] Re: [MIR] nullboot

[Ioanna Alifieraki]

Review for Package: nullboot

[Summary]
nullboot is a boot manager for environments that do not need a boot manager. 
Instead of running a boot manager at boot, it directly manages the UEFI boot 
entries for you.
It produces a Go binary that measures boot binaries and does some sealing, 
to allow automatic full disk encryption. 
It only operates on trusted data (firmware data and kernels in 
/usr/lib/linux/efi).

MIR team ACK

This does need a security review, so I'll assign ubuntu-security
(package deals with security attestation)

List of specific binary packages to be promoted to main:
nullboot_0.3.0-0ubuntu1_amd64

Notes:
Recommended TODOs:
1. It would be nice to have a test plan for end-to-end testing.

- The package should get a team bug subscriber before being promoted


[Duplication]
- There is no other package in main providing the same functionality.

[Dependencies]
OK:
- no other Dependencies to MIR due to this
- checked with check-mir
- not listed in seeded-in-ubuntu
- none of the (potentially auto-generated) dependencies (Depends
  and Recommends) that are present after build are not in main
- no -dev/-debug/-doc packages that need exclusion
- No dependencies in main that are only superficially tested requiring
   more tests now.

Problems: None

[Embedded sources and static linking]
OK:
- does not have odd Built-Using entries
- Go Package that follows the Debian Go packaging guidelines
- vendoring is used, but the reasoning is sufficiently explained
- golang: static builds are used, the team confirmed their commitment
   to the additional responsibilities implied by static builds.

Problems: None

[Security]
OK:
- history of CVEs does not look concerning
- does not run a daemon as root
- does not use webkit1,2
- does not use lib*v8 directly
- does not parse data formats
- does not open a port/socket
- does not process arbitrary web content
- does not use centralized online accounts
- does not integrate arbitrary javascript into the desktop
- does not deal with system authentication (eg, pam), etc)

Problems:
- does deal with security attestation (secure boot, tpm, signatures)


[Common blockers]
OK:
- does not FTBFS currently
- does have a test suite that runs at build time
- test suite fails will fail the build upon error.
- does have a non-trivial test suite that runs as autopkgtest
- no new python2 dependency
- Go package, but using dh-golang

Problems: None

[Packaging red flags]
OK:
- Ubuntu does not carry a delta
- symbols tracking not applicable for this kind of code.
- d/watch is present and looks ok (if needed, e.g. non-native)
- Upstream update history is good
- Debian/Ubuntu update history is good
- the current release is packaged
- promoting this does not seem to cause issues for MOTUs that so far
   maintained the package
- no massive Lintian warnings
- d/rules is rather clean
- It is not on the lto-disabled list

Problems: None

[Upstream red flags]
OK:
- no Errors/warnings during the build
- no incautious use of malloc/sprintf (as far as we can check it)
- no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH (usage is OK inside
   tests)
- no use of user nobody
- no use of setuid
- no important open bugs (crashers, etc) in Debian or Ubuntu
- no dependency on webkit, qtwebkit, seed or libgoa-*
- not part of the UI for extra checks
- no translation present, but none needed for this case (user visible)?

Problems: None

** Changed in: nullboot (Ubuntu)
 Assignee: Ioanna Alifieraki (joalif) => (unassigned)

** Changed in: nullboot (Ubuntu)
 Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965115

Title:
  [MIR] nullboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nullboot/+bug/1965115/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1964600] Re: [MIR] gnome-bluetooth3

[Ioanna Alifieraki]

Review for Package: gnome-bluetooth3

[Summary]
MIR team ACK under the constraint to resolve the below listed
required TODOs and as much as possible having a look at the
recommended TODOs.

This does not need a security review

List of specific binary packages to be promoted to main:
libgnome-bluetooth-3.0-13
libgnome-bluetooth-ui-3.0-13
libgnome-bluetooth-3.0-dev
libgnome-bluetooth-ui-3.0-dev
gir1.2-gnomebluetooth-3.0
libgnome-bluetooth-doc
gnome-bluetooth-3-common

Notes:

Required TODOs:
1. Add some autopackage tests
2.The package should get a team bug subscriber before being promoted

Recommended TODOs:
- Fix the the build warnings upstream ( 
https://pastebin.canonical.com/p/dKrn86DtDY/ )


[Duplication]
- There is no other package in main providing the same functionality 
IIUC gnome-bluetooth which is already in main provides the same functionality, 
however the analysis in the [Background information] in bug description seems 
convincing to promote gnome-bluetooth3 to main along side gnome-bluethooth 
which will be demoted in 20.10.

[Dependencies]
OK:
- no other Dependencies to MIR due to this
- no -dev/-debug/-doc packages that need exclusion
- No dependencies in main that are only superficially tested requiring
  more tests now.

Problems: None

[Embedded sources and static linking]
OK:
- no embedded source present
- no static linking
- does not have odd Built-Using entries
- not a go package, no extra constraints to consider in that regard
- No vendoring used, all Built-Using are in main

Problems: None

[Security]
OK:
- history of CVEs does not look concerning
- does not run a daemon as root
- does not use webkit1,2
- does not use lib*v8 directly
- does not open a port/socket
- does not parse data formats
- does not process arbitrary web content
- does not use centralized online accounts
- does not integrate arbitrary javascript into the desktop
- does not deal with system authentication (eg, pam), etc)
- does not deal with security attestation (secure boot, tpm, signatures)

Problems: None

[Common blockers]
OK:
- does not FTBFS currently
- does have a test suite that runs at build time
  - test suite fails will fail the build upon error.
- no new python2 dependency

Problems:
- does not have test suite that runs as autopkgtest

[Packaging red flags]
OK:
- Ubuntu does not carry a delta
- symbols tracking is in place
- d/watch is present and looks ok (if needed, e.g. non-native)
- Upstream update history is good
- Debian/Ubuntu update history is good
- the current release is packaged
- promoting this does not seem to cause issues for MOTUs that so far
  maintained the package
- no massive Lintian warnings
- d/rules is rather clean
- It is not on the lto-disabled list

Problems: None

[Upstream red flags]
OK:
- no incautious use of malloc/sprintf (as far as we can check it)
- no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH (usage is OK inside
   tests)
- no use of user nobody
- no use of setuid
- no important open bugs (crashers, etc) in Debian or Ubuntu
- no dependency on webkit, qtwebkit, seed or libgoa-*
- part of the UI, desktop file is ok
- translation present

Problems:
- Errors/warnings during the build
  - Upstream build produces the following warnings :
https://pastebin.canonical.com/p/dKrn86DtDY/


** Changed in: gnome-bluetooth3 (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964600

Title:
  [MIR] gnome-bluetooth3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth3/+bug/1964600/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1964600] Re: [MIR] gnome-bluetooth3

[Ioanna Alifieraki]

** Changed in: gnome-bluetooth3 (Ubuntu)
 Assignee: (unassigned) => Ioanna Alifieraki (joalif)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964600

Title:
  [MIR] gnome-bluetooth3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth3/+bug/1964600/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887187] Re: [MIR] nftables

[Ioanna Alifieraki]

** Changed in: nftables (Ubuntu)
 Assignee: (unassigned) => Ioanna Alifieraki (joalif)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887187

Title:
  [MIR] nftables

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nftables/+bug/1887187/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1958293] Re: [MIR]: libyang2

[Ioanna Alifieraki]

Review for Package: src:libyang2

[Summary]
libyang2 source package is a parser toolkit for IETF YANG data modelling.
It provides :
* the library (libyang2) which implements functions to process schemas 
expressed in 
YANG data modelling language. The schemas primarily describe network equipment 
configuration.
* development files (libyang2-dev)
* executable tools (libyang2-tools, libyang-tools) which can be used for the 
creation
of IETF YANG schemas.

MIR team ACK

This does need a security review because it parses data formats, so I'll
assign ubuntu-security.

List of specific binary packages to be promoted to main: libyang2, libyang2-dev 
Specific binary packages built, but NOT to be promoted to main: libyang2-tools, 
libyang-tools (no dependency on them)

Notes:
Recommended TODOs:
- The package provides one autopackage test. It would be nice to have more.
- In the buildlog 
(https://launchpadlibrarian.net/581476001/buildlog_ubuntu-jammy-amd64.libyang2_2.0.112-6ubuntu1_BUILDING.txt.gz)
  there are 2 warnings reported many times. It would be nice to report them 
upstream to be fixed.
  The warnings are :
  ../.././src/parser_json.c: In function ‘lydjson_data_skip’:
  ../.././src/parser_json.c:304:46: warning: ‘current’ may be used 
uninitialized in this function [-Wmaybe-uninitialized]
  ../.././src/parser_json.c:283:39: note: ‘current’ was declared here

  ../.././src/schema_compile_node.c: In function ‘lys_compile_node_’:
  ../.././src/schema_compile_node.c:2438:19: warning: ‘list’ may be used 
uninitialized in this function [-Wmaybe-uninitialized]
  ../.././src/schema_compile_node.c:2426:28: note: ‘list’ was declared here

[Duplication]
- There is no other package in main providing the same functionality.

[Dependencies]
OK:
- no other Dependencies to MIR due to this
  - checked with check-mir
  - not listed in seeded-in-ubuntu
  - none of the (potentially auto-generated) dependencies (Depends
and Recommends) that are present after build are not in main
- no -dev/-debug/-doc packages that need exclusion
- No dependencies in main that are only superficially tested requiring
   more tests now.

Problems: None

[Embedded sources and static linking]
OK:
- no embedded source present
- no static linking
- does not have odd Built-Using entries
- not a go package, no extra constraints to consider in that regard
- No vendoring used, all Built-Using are in main

Problems: None

[Security]

OK:
- history of CVEs does not look concerning
- does not run a daemon as root
- does not use webkit1,2
- does not use lib*v8 directly
- does not open a port/socket
- does not process arbitrary web content
- does not use centralized online accounts
- does not integrate arbitrary javascript into the desktop
- does not deal with system authentication (eg, pam), etc)
- does not deal with security attestation (secure boot, tpm, signatures)

Problems:
- package does parse data-formats

[Common blockers]
OK:
- does not FTBFS currently
- does have a test suite that runs at build time
- test suite fails will fail the build upon error.
- does have a non-trivial test suite that runs as autopkgtest
- no new python2 dependency

Problems: None

[Packaging red flags]
OK:
- Ubuntu does carry a delta, but it is reasonable and maintenance under
  control
- symbols tracking is in place
- d/watch is present and looks ok (if needed, e.g. non-native)
- Upstream update history is good
- Debian/Ubuntu update history is good
- the current release is packaged
- promoting this does not seem to cause issues for MOTUs that so far
   maintained the package
- no massive Lintian warnings
- d/rules is rather clean
- It is not on the lto-disabled list

Problems: None

[Upstream red flags]

OK:
- no Errors/warnings during the build
- no incautious use of malloc/sprintf (as far as we can check it)
- no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH (usage is OK inside
   tests)
- no use of user nobody
- no use of setuid
- no important open bugs (crashers, etc) in Debian or Ubuntu
- no dependency on webkit, qtwebkit, seed or libgoa-*
- not part of the UI for extra checks

Problems: None

** Changed in: libyang2 (Ubuntu)
 Assignee: Ioanna Alifieraki (joalif) => Ubuntu Security Team 
(ubuntu-security)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958293

Title:
  [MIR]: libyang2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libyang2/+bug/1958293/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1958293] Re: [MIR]: libyang2

[Ioanna Alifieraki]

** Changed in: libyang2 (Ubuntu)
 Assignee: (unassigned) => Ioanna Alifieraki (joalif)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958293

Title:
  [MIR]: libyang2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libyang2/+bug/1958293/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1950666] Re: system crash when removing ipmi_msghandler module

[Ioanna Alifieraki]

VERIFICATION

User that reported the issue has tested from -proposed and confirmed
that it works.

** Tags removed: verification-needed-focal verification-needed-hirsute 
verification-needed-impish
** Tags added: verification-done-focal verification-done-hirsute 
verification-done-impish

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950666

Title:
  system crash when removing ipmi_msghandler module

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950666/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1955129] Re: trace-cmd report buffer overflow detected

[Ioanna Alifieraki]

Debdiff for Bionic

** Patch added: "lp1955129_bionic.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/trace-cmd/+bug/1955129/+attachment/5548307/+files/lp1955129_bionic.debdiff

** Tags added: sts

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1955129

Title:
  trace-cmd report buffer overflow detected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/trace-cmd/+bug/1955129/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1955129] Re: trace-cmd report buffer overflow detected

[Ioanna Alifieraki]

Debdiff for Bionic

** Patch added: "lp1955129_bionic.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/trace-cmd/+bug/1955129/+attachment/5548306/+files/lp1955129_bionic.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1955129

Title:
  trace-cmd report buffer overflow detected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/trace-cmd/+bug/1955129/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1955129] [NEW] trace-cmd report buffer overflow detected

[Ioanna Alifieraki]

Public bug reported:

[IMPACT]

When running trace-cmd report on Bionic it crashes with

*** buffer overflow detected ***: trace-cmd terminated
Aborted (core dumped)


[TEST CASE]

Prepare a simple script to trace e.g. :

#!/usr/bin/python
import socket
s = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
s.close()

then

$ sudo trace-cmd record -a -p function_graph -g __fput -g sock_close -g
tcp_close python2 ./close.py

$ sudo trace-cmd report

The latter will fail with buffer overflow detected


[WHERE THINGS COULD GO WRONG]

The fixing commit changes the size of a buffer from 20 to 24 in arg_eval() 
function
to avoid buffer overflow.
Any potential regression would occur in that function.


[OTHER]

Only Bionic is affected, it is fixed in newer releases.

Fix upstream commit 1375d98d8017e371776adbef10122a57ce2100e5

** Affects: trace-cmd (Ubuntu)
 Importance: Medium
 Assignee: Ioanna Alifieraki (joalif)
 Status: In Progress

** Affects: trace-cmd (Ubuntu Bionic)
 Importance: Medium
 Assignee: Ioanna Alifieraki (joalif)
 Status: In Progress

** Changed in: trace-cmd (Ubuntu)
   Status: New => In Progress

** Changed in: trace-cmd (Ubuntu)
   Importance: Undecided => Medium

** Changed in: trace-cmd (Ubuntu)
 Assignee: (unassigned) => Ioanna Alifieraki (joalif)

** Also affects: trace-cmd (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: trace-cmd (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: trace-cmd (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: trace-cmd (Ubuntu Bionic)
 Assignee: (unassigned) => Ioanna Alifieraki (joalif)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1955129

Title:
  trace-cmd report buffer overflow detected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/trace-cmd/+bug/1955129/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1950666] Re: system crash when removing ipmi_msghandler module

[Ioanna Alifieraki]

** Description changed:

  [IMPACT]
  
  Commit 3b9a907223d7 (ipmi: fix sleep-in-atomic in free_user at cleanup SRCU 
user->release_barrier)
  pushes the removal of an ipmi_user into the system's workqueue.
  
  Whenever an ipmi_user struct is about to be removed it is scheduled as a
  work on the system's workqueue to guarantee the free operation won't be
  executed in atomic context. When the work is executed the
  free_user_work() function is invoked which frees the ipmi_user.
  
  When ipmi_msghandler module is removed in cleanup_ipmi() function, there is 
no check if there are any pending works to be executed.
  Therefore, there is a potential race condition :
  An ipmi_user is scheduled for removal and shortly after to remove the 
ipmi_msghandler module.
  If the scheduled work delays execution for any reason and the module is 
removed first, then when the work is executed the pages of free_user_work() are 
gone and the system crashes with the following :
  
  BUG: unable to handle page fault for address: c05c3450
  #PF: supervisor instruction fetch in kernel mode
  #PF: error_code(0x0010) - not-present page
  PGD 635420e067 P4D 635420e067 PUD 6354210067 PMD 4711e51067 PTE 0
  Oops: 0010 [#1] SMP PTI
  CPU: 19 PID: 29646 Comm: kworker/19:1 Kdump: loaded Not tainted 
5.4.0-77-generic #86~18.04.1-Ubuntu
  Hardware name: Ciara Technologies ORION RS610-G4-DTH4S/MR91-FS1-Y9, BIOS F29 
05/23/2019
  Workqueue: events 0xc05c3450
  RIP: 0010:0xc05c3450
  Code: Bad RIP value.
  RSP: 0018:b721333c3e88 EFLAGS: 00010286
  RAX: c05c3450 RBX: 92a95f56a740 RCX: b7221cfd14e8
  RDX: 0001 RSI: 92616040d4b0 RDI: b7221cf404e0
  RBP: b721333c3ec0 R08: 73746e657665 R09: 8080808080808080
  R10: b721333c3de0 R11: fefefefefefefeff R12: 92a95f570700
  R13: 92a0a40ece40 R14: b7221cf404e0 R15: 092a95f57070
  FS: () GS:92a95f54() knlGS:
  CS: 0010 DS:  ES:  CR0: 80050033
  CR2: c05c3426 CR3: 0081e9bfc005 CR4: 007606e0
  DR0:  DR1:  DR2: 
  DR3:  DR6: fffe0ff0 DR7: 0400
  PKRU: 5554
  Call Trace:
  ? process_one_work+0x20f/0x400
  worker_thread+0x34/0x410
  kthread+0x121/0x140
  ? process_one_work+0x400/0x400
  ? kthread_park+0x90/0x90
  ret_from_fork+0x35/0x40
  Modules linked in: xt_REDIRECT xt_owner ipt_rpfilter xt_CT xt_multiport 
xt_set ip_set_hash_ip veth xt_statistic ipt_REJECT
  ... megaraid_sas ahci libahci wmi [last unloaded: ipmi_msghandler]
  CR2: c05c3450
  
  [TEST CASE]
  
  The user who reported the issue can reproduce reliably by stopping the ipmi 
related services and then removing the ipmi modules.
  I could reproduce the issue only when turning the normal 'work' to delayed 
work.
  
  [WHERE PROBLEMS COULD OCCUR]
  
- TBD
+ The fixing patch creates a dedicated workqueue for the remove_work
+ struct of ipmi_user when loading the ipmi_msghandler modules and
+ destroys the workqueue when removing the module. Therefore any potential
+ problems would occur during these two operations or when scheduling
+ works on the dedicated workqueue.
  
  [OTHER]
  
- Upstream is affected too, working on a patch to address this.
+ Upstream patches : 
+ 1d49eb91e86e (ipmi: Move remove_work to dedicated workqueue)
+ 5a3ba99b62d8 (ipmi: msghandler: Make symbol 'remove_work_wq' static)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950666

Title:
  system crash when removing ipmi_msghandler module

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950666/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927519] Re: Mitigate libvirt: error : unable to set AppArmor profile 'libvirt-' for '/usr/bin/kvm-spice': No such file or directory

[Ioanna Alifieraki]

VERIFICATION USSURI

Installed libvirt form ussuri-proposed

dpkg -l | grep libvirt

ii  libvirt-clients6.0.0-0ubuntu8.15~cloud0 
   amd64Programs for the libvirt library
ii  libvirt-daemon 6.0.0-0ubuntu8.15~cloud0 
   amd64Virtualization daemon
ii  libvirt-daemon-driver-qemu 6.0.0-0ubuntu8.15~cloud0 
   amd64Virtualization daemon QEMU connection driver
ii  libvirt-daemon-driver-storage-rbd  6.0.0-0ubuntu8.15~cloud0 
   amd64Virtualization daemon RBD storage driver
ii  libvirt-daemon-system  6.0.0-0ubuntu8.15~cloud0 
   amd64Libvirt daemon configuration files
ii  libvirt-daemon-system-systemd  6.0.0-0ubuntu8.15~cloud0 
   amd64Libvirt daemon configuration files (systemd)
ii  libvirt0:amd64 6.0.0-0ubuntu8.15~cloud0 
   amd64library for interfacing with different 
virtualization systems

# virsh dominfo debiantesting
Id: -
Name:   debiantesting
UUID:   47340dd6-80e2-4d14-bdc9-bb2c7564079a
OS Type:hvm
State:  shut off
CPU(s): 1
Max memory: 1048576 KiB
Used memory:1048576 KiB
Persistent: yes
Autostart:  disable
Managed save:   no
Security model: apparmor
Security DOI:   0


# cat /dev/null | sudo tee
/etc/apparmor.d/libvirt/libvirt-47340dd6-80e2-4d14-bdc9-bb2c7564079a

# virsh start debiantesting
Domain debiantesting started

** Tags removed: sts-sru-sponsor verification-queens-needed 
verification-stein-needed verification-ussuri-needed
** Tags added: verification-queens-done verification-stein-done 
verification-ussuri-done

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927519

Title:
  Mitigate libvirt: error : unable to set AppArmor profile 'libvirt-' for '/usr/bin/kvm-spice': No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1927519/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927519] Re: Mitigate libvirt: error : unable to set AppArmor profile 'libvirt-' for '/usr/bin/kvm-spice': No such file or directory

[Ioanna Alifieraki]

VERIFICATION STEIN

Installed libvirt form stein-proposed

dpkg -l | grep libvirt

ii  libvirt-clients5.0.0-1ubuntu2.6~cloud3  
   amd64Programs for the libvirt library
ii  libvirt-daemon 5.0.0-1ubuntu2.6~cloud3  
   amd64Virtualization daemon
ii  libvirt-daemon-driver-storage-rbd  5.0.0-1ubuntu2.6~cloud3  
   amd64Virtualization daemon RBD storage driver
ii  libvirt-daemon-system  5.0.0-1ubuntu2.6~cloud3  
   amd64Libvirt daemon configuration files
ii  libvirt0:amd64 5.0.0-1ubuntu2.6~cloud3  
   amd64library for interfacing with different 
virtualization systems


# virsh dominfo debiantesting
Id: -
Name:   debiantesting
UUID:   47340dd6-80e2-4d14-bdc9-bb2c7564079a
OS Type:hvm
State:  shut off
CPU(s): 1
Max memory: 1048576 KiB
Used memory:1048576 KiB
Persistent: yes
Autostart:  disable
Managed save:   no
Security model: apparmor
Security DOI:   0


# cat /dev/null | sudo tee 
/etc/apparmor.d/libvirt/libvirt-47340dd6-80e2-4d14-bdc9-bb2c7564079a

# virsh start debiantesting
Domain debiantesting started

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927519

Title:
  Mitigate libvirt: error : unable to set AppArmor profile 'libvirt-' for '/usr/bin/kvm-spice': No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1927519/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927519] Re: Mitigate libvirt: error : unable to set AppArmor profile 'libvirt-' for '/usr/bin/kvm-spice': No such file or directory

[Ioanna Alifieraki]

VERIFICATION QUEENS

Installed libvirt form queens-proposed

dpkg -l | grep libvirt

ii  libvirt-bin4.0.0-1ubuntu8.20~cloud0 
   amd64programs for the libvirt library
ii  libvirt-clients4.0.0-1ubuntu8.20~cloud0 
   amd64Programs for the libvirt library
ii  libvirt-daemon 4.0.0-1ubuntu8.20~cloud0 
   amd64Virtualization daemon
ii  libvirt-daemon-driver-storage-rbd  4.0.0-1ubuntu8.20~cloud0 
   amd64Virtualization daemon RBD storage driver
ii  libvirt-daemon-system  4.0.0-1ubuntu8.20~cloud0 
   amd64Libvirt daemon configuration files
ii  libvirt0:amd64 4.0.0-1ubuntu8.20~cloud0 
   amd64library for interfacing with different virtualization 
systems


# virsh dominfo ctest1
Id: -
Name:   ctest1
UUID:   2fadfa2d-28d8-4bbc-8b31-dfb871881b7e
OS Type:hvm
State:  shut off
CPU(s): 1
Max memory: 1048576 KiB
Used memory:1048576 KiB
Persistent: yes
Autostart:  disable
Managed save:   no
Security model: apparmor
Security DOI:   0


#  cat /dev/null | sudo tee 
/etc/apparmor.d/libvirt/libvirt-2fadfa2d-28d8-4bbc-8b31-dfb871881b7e

# virsh start ctest1
Domain ctest1 started

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927519

Title:
  Mitigate libvirt: error : unable to set AppArmor profile 'libvirt-' for '/usr/bin/kvm-spice': No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1927519/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927519] Re: Mitigate libvirt: error : unable to set AppArmor profile 'libvirt-' for '/usr/bin/kvm-spice': No such file or directory

[Ioanna Alifieraki]

Debdiff for Ussuri

** Patch added: "lp1927519_ussuri.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1927519/+attachment/5542092/+files/lp1927519_ussuri.debdiff

** Tags added: sts-sru-sponsor

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927519

Title:
  Mitigate libvirt: error : unable to set AppArmor profile 'libvirt-' for '/usr/bin/kvm-spice': No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1927519/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927519] Re: Mitigate libvirt: error : unable to set AppArmor profile 'libvirt-' for '/usr/bin/kvm-spice': No such file or directory

[Ioanna Alifieraki]

Debdiff for Stein.

** Patch added: "lp1927519_stein.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1927519/+attachment/5542091/+files/lp1927519_stein.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927519

Title:
  Mitigate libvirt: error : unable to set AppArmor profile 'libvirt-' for '/usr/bin/kvm-spice': No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1927519/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927519] Re: Mitigate libvirt: error : unable to set AppArmor profile 'libvirt-' for '/usr/bin/kvm-spice': No such file or directory

[Ioanna Alifieraki]

Debdiff for Stein.

** Patch added: "lp1927519_stein.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1927519/+attachment/5542090/+files/lp1927519_stein.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927519

Title:
  Mitigate libvirt: error : unable to set AppArmor profile 'libvirt-' for '/usr/bin/kvm-spice': No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1927519/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927519] Re: Mitigate libvirt: error : unable to set AppArmor profile 'libvirt-' for '/usr/bin/kvm-spice': No such file or directory

[Ioanna Alifieraki]

Debdiff for Stein.

** Patch added: "lp1927519_stein.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1927519/+attachment/5542089/+files/lp1927519_stein.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927519

Title:
  Mitigate libvirt: error : unable to set AppArmor profile 'libvirt-' for '/usr/bin/kvm-spice': No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1927519/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927519] Re: Mitigate libvirt: error : unable to set AppArmor profile 'libvirt-' for '/usr/bin/kvm-spice': No such file or directory

[Ioanna Alifieraki]

Debdiff for Queens

** Patch added: "lp1927519_queens.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1927519/+attachment/5542088/+files/lp1927519_queens.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927519

Title:
  Mitigate libvirt: error : unable to set AppArmor profile 'libvirt-' for '/usr/bin/kvm-spice': No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1927519/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927519] Re: Mitigate libvirt: error : unable to set AppArmor profile 'libvirt-' for '/usr/bin/kvm-spice': No such file or directory

[Ioanna Alifieraki]

@Christian,

Thank you very much for uploading in Jammy and SRUs.
I am preparing the debdiffs for the UCA.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927519

Title:
  Mitigate libvirt: error : unable to set AppArmor profile 'libvirt-' for '/usr/bin/kvm-spice': No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1927519/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1950666] [NEW] system crash when removing ipmi_msghandler module

[Ioanna Alifieraki]

Public bug reported:

[IMPACT]

Commit 3b9a907223d7 (ipmi: fix sleep-in-atomic in free_user at cleanup SRCU 
user->release_barrier)
pushes the removal of an ipmi_user into the system's workqueue.

Whenever an ipmi_user struct is about to be removed it is scheduled as a
work on the system's workqueue to guarantee the free operation won't be
executed in atomic context. When the work is executed the
free_user_work() function is invoked which frees the ipmi_user.

When ipmi_msghandler module is removed in cleanup_ipmi() function, there is no 
check if there are any pending works to be executed.
Therefore, there is a potential race condition :
An ipmi_user is scheduled for removal and shortly after to remove the 
ipmi_msghandler module.
If the scheduled work delays execution for any reason and the module is removed 
first, then when the work is executed the pages of free_user_work() are gone 
and the system crashes with the following :

BUG: unable to handle page fault for address: c05c3450
#PF: supervisor instruction fetch in kernel mode
#PF: error_code(0x0010) - not-present page
PGD 635420e067 P4D 635420e067 PUD 6354210067 PMD 4711e51067 PTE 0
Oops: 0010 [#1] SMP PTI
CPU: 19 PID: 29646 Comm: kworker/19:1 Kdump: loaded Not tainted 
5.4.0-77-generic #86~18.04.1-Ubuntu
Hardware name: Ciara Technologies ORION RS610-G4-DTH4S/MR91-FS1-Y9, BIOS F29 
05/23/2019
Workqueue: events 0xc05c3450
RIP: 0010:0xc05c3450
Code: Bad RIP value.
RSP: 0018:b721333c3e88 EFLAGS: 00010286
RAX: c05c3450 RBX: 92a95f56a740 RCX: b7221cfd14e8
RDX: 0001 RSI: 92616040d4b0 RDI: b7221cf404e0
RBP: b721333c3ec0 R08: 73746e657665 R09: 8080808080808080
R10: b721333c3de0 R11: fefefefefefefeff R12: 92a95f570700
R13: 92a0a40ece40 R14: b7221cf404e0 R15: 092a95f57070
FS: () GS:92a95f54() knlGS:
CS: 0010 DS:  ES:  CR0: 80050033
CR2: c05c3426 CR3: 0081e9bfc005 CR4: 007606e0
DR0:  DR1:  DR2: 
DR3:  DR6: fffe0ff0 DR7: 0400
PKRU: 5554
Call Trace:
? process_one_work+0x20f/0x400
worker_thread+0x34/0x410
kthread+0x121/0x140
? process_one_work+0x400/0x400
? kthread_park+0x90/0x90
ret_from_fork+0x35/0x40
Modules linked in: xt_REDIRECT xt_owner ipt_rpfilter xt_CT xt_multiport xt_set 
ip_set_hash_ip veth xt_statistic ipt_REJECT
... megaraid_sas ahci libahci wmi [last unloaded: ipmi_msghandler]
CR2: c05c3450

[TEST CASE]

The user who reported the issue can reproduce reliably by stopping the ipmi 
related services and then removing the ipmi modules.
I could reproduce the issue only when turning the normal 'work' to delayed work.

[WHERE PROBLEMS COULD OCCUR]

TBD

[OTHER]

Upstream is affected too, working on a patch to address this.

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Ioanna Alifieraki (joalif)
 Status: In Progress

** Affects: linux (Ubuntu Focal)
 Importance: Medium
 Assignee: Ioanna Alifieraki (joalif)
 Status: Confirmed

** Affects: linux (Ubuntu Hirsute)
 Importance: Medium
 Assignee: Ioanna Alifieraki (joalif)
 Status: Confirmed

** Affects: linux (Ubuntu Impish)
 Importance: Medium
 Assignee: Ioanna Alifieraki (joalif)
 Status: Confirmed

** Affects: linux (Ubuntu Jammy)
 Importance: Medium
 Assignee: Ioanna Alifieraki (joalif)
 Status: In Progress

** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Impish)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Focal)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Hirsute)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Impish)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Jammy)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Focal)
   Status: New => Confirmed

** Changed in: linux (Ubuntu Hirsute)
   Status: New => Confirmed

** Changed in: linux (Ubuntu Impish)
   Status: New => Confirmed

** Changed in: linux (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: linux (Ubuntu Jammy)
 Assignee: (unassigned) => Ioanna Alifieraki (joalif)

** Changed in: linux (Ubuntu Impish)
 Assignee: (unassigned) => Ioanna Alifieraki (joalif)

** Changed in: linux (Ubuntu Hirsute)
 Assignee: (unassigned) => Ioanna Alifieraki (joalif)

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Ioanna Alifieraki (joalif)

** Description changed:

  [IMPACT]
  
  Commit 3b9a907223d7 (ipmi: fix sleep-in-atomic in free_user at cleanup S

[Bug 1927519] Re: Mitigate libvirt: error : unable to set AppArmor profile 'libvirt-' for '/usr/bin/kvm-spice': No such file or directory

[Ioanna Alifieraki]

** Also affects: libvirt (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: libvirt (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Also affects: libvirt (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: libvirt (Ubuntu Impish)
   Importance: Undecided
   Status: New

** Also affects: libvirt (Ubuntu Jammy)
   Importance: Medium
   Status: Confirmed

** Changed in: libvirt (Ubuntu Impish)
   Status: New => Confirmed

** Changed in: libvirt (Ubuntu Hirsute)
   Status: New => Confirmed

** Changed in: libvirt (Ubuntu Focal)
   Status: New => Confirmed

** Changed in: libvirt (Ubuntu Bionic)
   Status: New => Confirmed

** Changed in: libvirt (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: libvirt (Ubuntu Focal)
   Importance: Undecided => Medium

** Changed in: libvirt (Ubuntu Hirsute)
   Importance: Undecided => Medium

** Changed in: libvirt (Ubuntu Impish)
   Importance: Undecided => Medium

** Also affects: cloud-archive
   Importance: Undecided
   Status: New

** Also affects: cloud-archive/queens
   Importance: Undecided
   Status: New

** Also affects: cloud-archive/ussuri
   Importance: Undecided
   Status: New

** Also affects: cloud-archive/stein
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927519

Title:
  Mitigate libvirt: error : unable to set AppArmor profile 'libvirt-' for '/usr/bin/kvm-spice': No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1927519/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921403] Re: makedumpfile does not create dmesg file in /var/crash on 5.10+ kernels

[Ioanna Alifieraki]

VERIFICATION FOCAL

Installed makedumpfile from proposed.
Testing on a Focal machine running 5.11 kernel.

# uname -rv
5.11.0-40-generic #44~20.04.1-Ubuntu SMP Wed Oct 20 19:04:34 UTC 2021

Trigger crash:
# echo 1 > /proc/sys/kernel/sysrq 
# echo c > /proc/sysrq-trigger

After reboot contents of /var/crash :
/var/crash/202110271414# ls
dmesg.202110271414  dump.202110271414

dmesg file has been successfully created.

** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921403

Title:
  makedumpfile does not create dmesg file in /var/crash on 5.10+ kernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1921403/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1942784] Re: makedumpfile falls back to cp on focal with 5.11 kernel

[Ioanna Alifieraki]

VERIFICATION ON FOCAL

Installed makedumpfile from proposed.
Testing on a Focal machine running 5.11 kernel.

# uname -rv
5.11.0-40-generic #44~20.04.1-Ubuntu SMP Wed Oct 20 19:04:34 UTC 2021

Trigger crash:
# echo 1 > /proc/sys/kernel/sysrq 
# echo c > /proc/sysrq-trigger

From console output :

[   57.418037] kdump-tools[548]: Starting kdump-tools:
[   57.419099] kdump-tools[554]:  * running makedumpfile -c -d 31 /proc/vmcore 
/var/crash/202110271414/dump-incomplete
Copying data  : [100.0 %] /   eta: 
0s
[   61.481957] kdump-tools[572]: The kernel version is not supported.
[   61.494134] kdump-tools[572]: The makedumpfile operation may be incomplete.
[   61.501242] kdump-tools[572]: The dumpfile is saved to 
/var/crash/202110271414/dump-incomplete.
[   61.502711] kdump-tools[572]: makedumpfile Completed.
[   61.503885] kdump-tools[554]:  * kdump-tools: saved vmcore in 
/var/crash/202110271414
[   61.851266] kdump-tools[554]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/202110271414/dmesg.202110271414
[   61.867626] kdump-tools[576]: The kernel version is not supported.
[   61.871305] kdump-tools[576]: The makedumpfile operation may be incomplete.
[   61.877902] kdump-tools[576]: The dmesg log is saved to 
/var/crash/202110271414/dmesg.202110271414.
[   61.881797] kdump-tools[576]: makedumpfile Completed.
[   61.885645] kdump-tools[554]:  * kdump-tools: saved dmesg content in 
/var/crash/202110271414
[   61.989595] kdump-tools[579]: Wed, 27 Oct 2021 14:14:21 +
[   62.123243] kdump-tools[580]: Rebooting.
[   62.561341] reboot: Restarting system

Makedumpfile compress the dump and does not fall back to cp.

** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942784

Title:
  makedumpfile falls back to cp on focal with 5.11 kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1942784/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921403] Re: makedumpfile does not create dmesg file in /var/crash on 5.10+ kernels

[Ioanna Alifieraki]

** Description changed:

  [IMPACT]
- 
  makedumpfile does not create the dmesg. in /var/crash.
  This happens only on 5.10+ kernel because 5.10 kernel introduces a new
  lockless ringbuffer.
- 
- [FIX]
  
  This issue has been addressed upstream with commits :
  [1] c617ec633392([PATCH 1/2] printk: add support for lockless ringbuffer)
  [2] 44b073b7ec46([PATCH 2/2] printk: use committed/finalized state values)
  
  [TEST CASE]
  
  For testing a machine running focal with the 5.11 kernel is required.
  Then trigger a crash.
  After reboot make sure that dmesg. file is created in 
/var/crash/
  
  [WHERE PROBLEMS COULD OCCUR]
  
  Any problems would involve the dmesg file not created.
  
  [Other]
  
  [1] 
https://github.com/makedumpfile/makedumpfile/commit/c617ec63339222f3a44d73e36677a9acc8954ccd
  [2] 
https://github.com/makedumpfile/makedumpfile/commit/44b073b7ec467aee0d7de381d455b8ace1199184

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921403

Title:
  makedumpfile does not create dmesg file in /var/crash on 5.10+ kernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1921403/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921403] Re: makedumpfile does not create dmesg file in /var/crash on 5.10+ kernels

[Ioanna Alifieraki]

** Description changed:

+ 
+ [DESCRIPTION]
  makedumpfile does not create the dmesg. in /var/crash.
  This happens only on 5.10+ kernel because 5.10 kernel introduces a new
  lockless ringbuffer.
  
  This issue has been addressed upstream with commits :
  [1] c617ec633392([PATCH 1/2] printk: add support for lockless ringbuffer)
  [2] 44b073b7ec46([PATCH 2/2] printk: use committed/finalized state values)
  
+ [TEST CASE]
+ 
+ For testing a machine running focal with the 5.11 kernel is required.
+ Then trigger a crash.
+ After reboot make sure that dmesg. file is created in 
/var/crash/
+ 
+ [WHERE PROBLEMS COULD OCCUR]
+ 
+ Any problems would involve the dmesg file not created.
+ 
+ [Other]
+ 
  [1] 
https://github.com/makedumpfile/makedumpfile/commit/c617ec63339222f3a44d73e36677a9acc8954ccd
  [2] 
https://github.com/makedumpfile/makedumpfile/commit/44b073b7ec467aee0d7de381d455b8ace1199184

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921403

Title:
  makedumpfile does not create dmesg file in /var/crash on 5.10+ kernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1921403/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1942784] Re: makedumpfile not properly working on focal with 5.11 kernel

[Ioanna Alifieraki]

Tested new debdiff on Focal with 5.4 and 5.11 kernels, on amd64, arm64, ppc64el 
and s390x and
works as expected.
Making Hirsute 'Invalid' as all patches in new debdiff are already in H.

** Changed in: makedumpfile (Ubuntu Hirsute)
   Status: In Progress => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942784

Title:
  makedumpfile not properly working on focal with 5.11 kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1942784/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1942784] Re: makedumpfile not properly working on focal with 5.11 kernel

[Ioanna Alifieraki]

New debdiff for focal.

** Patch added: "lp1942784_focal.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1942784/+attachment/5535296/+files/lp1942784_focal.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942784

Title:
  makedumpfile not properly working on focal with 5.11 kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1942784/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1942784] Re: makedumpfile not properly working on focal with 5.11 kernel

[Ioanna Alifieraki]

** Description changed:

  [IMPACT]
  
  When running Focal with the hwe 5.11 kernel makedumpfile is not working as it 
should.
  Instead of compressing the dump makedumpfile falls back to cp.
  This can create problems on systems with very large RAM and result into 
exhausting all storage on the host.
- This can be resolved with upstream commit 54aec3878b3f([PATCH] make use of 
'uts_namespace.name' offset in VMCOREINFO).
+ This can be resolved with upstream commit f1197543d1c4 ([PATCH] Retrieve 
MAX_PHYSMEM_BITS from vmcoreinfo).
+ The reason for falling back to cp is that without this patch makedumpfile 
calculates wrongly the memory layout.
+ This happens after the kernel commit 1d50e5d0c505 ("crash_core, vmcoreinfo: 
Append 'MAX_PHYSMEM_BITS'to vmcoreinfo").
+ With this commit applied, reading MAX_PHYSMEM_BITS from vmcoreinfo instead of 
inferring lead to correctly detecting the memory layout and creating the dump 
file properly. 
  
  In addition the dmesg. is not created.
  This can be resolved with the following two commits  :
  - commit c617ec633392([PATCH 1/2] printk: add support for lockless ringbuffer)
  - commit 44b073b7ec46([PATCH 2/2] printk: use committed/finalized state 
values)
  
  [TEST CASE]
  
  For testing a machine running focal with the 5.11 kernel is required.
  Then trigger a crash.
- On the console we can see that makedumpfile fails and `falls back to cp`. 
+ On the console we can see that makedumpfile fails and `falls back to cp`.
  In /var/crash we can see that no dmesg file is created and instead of the 
dump file
  the uncompressed vmcoreinfo is created.
  
  [WHERE PROBLEMS COULD OCCUR]
  
  The 3 commits pulled into focal make makedumpfile compatible with the 5.11 
kernel.
  Any regression potential would involve the crash dump not being created after 
a crash in case kdump is configured.
  
  [OTHER]
  
  Only Focal with 5.11 kernel is affected.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942784

Title:
  makedumpfile not properly working on focal with 5.11 kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1942784/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1942784] Re: makedumpfile not properly working on focal with 5.11 kernel

[Ioanna Alifieraki]

@cascardo,

Good point, just tested it with 5.4 kernel and works fine with it too.

Thanks,
Jo

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942784

Title:
  makedumpfile not properly working on focal with 5.11 kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1942784/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1942784] Re: makedumpfile not properly working on focal with 5.11 kernel

[Ioanna Alifieraki]

** Tags added: sts

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942784

Title:
  makedumpfile not properly working on focal with 5.11 kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1942784/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1942784] Re: makedumpfile not properly working on focal with 5.11 kernel

[Ioanna Alifieraki]

Debdiff for Focal.

** Patch added: "lp1942784_focal.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1942784/+attachment/5523255/+files/lp1942784_focal.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942784

Title:
  makedumpfile not properly working on focal with 5.11 kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1942784/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1942784] [NEW] makedumpfile not properly working on focal with 5.11 kernel

[Ioanna Alifieraki]

Public bug reported:

[IMPACT]

When running Focal with the hwe 5.11 kernel makedumpfile is not working as it 
should.
Instead of compressing the dump makedumpfile falls back to cp.
This can create problems on systems with very large RAM and result into 
exhausting all storage on the host.
This can be resolved with upstream commit 54aec3878b3f([PATCH] make use of 
'uts_namespace.name' offset in VMCOREINFO).

In addition the dmesg. is not created.
This can be resolved with the following two commits  :
- commit c617ec633392([PATCH 1/2] printk: add support for lockless ringbuffer)
- commit 44b073b7ec46([PATCH 2/2] printk: use committed/finalized state values)

[TEST CASE]

For testing a machine running focal with the 5.11 kernel is required.
Then trigger a crash.
On the console we can see that makedumpfile fails and `falls back to cp`. 
In /var/crash we can see that no dmesg file is created and instead of the dump 
file
the uncompressed vmcoreinfo is created.

[WHERE PROBLEMS COULD OCCUR]

The 3 commits pulled into focal make makedumpfile compatible with the 5.11 
kernel.
Any regression potential would involve the crash dump not being created after a 
crash in case kdump is configured.

[OTHER]

Only Focal with 5.11 kernel is affected.

** Affects: makedumpfile (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: makedumpfile (Ubuntu Focal)
 Importance: Medium
 Assignee: Ioanna Alifieraki (joalif)
 Status: Confirmed

** Also affects: makedumpfile (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: makedumpfile (Ubuntu Focal)
 Assignee: (unassigned) => Ioanna Alifieraki (joalif)

** Changed in: makedumpfile (Ubuntu Focal)
   Importance: Undecided => Medium

** Changed in: makedumpfile (Ubuntu Focal)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942784

Title:
  makedumpfile not properly working on focal with 5.11 kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1942784/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL

[Ioanna Alifieraki]

** Tags removed: verification-needed verification-needed-groovy
** Tags added: verification-done verification-done-groovy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919275

Title:
  crash utility fails on arm64 with  cannot determine VA_BITS_ACTUAL

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1931435] Re: crash fails to build on ubuntu 20.10 (Groovy) on arm64

[Ioanna Alifieraki]

#VERIFICATION GROOVY

Package can now be built from source without erros.

** Tags removed: verification-needed verification-needed-groovy
** Tags added: verification-done verification-done-groovy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931435

Title:
  crash fails to build on ubuntu 20.10 (Groovy) on arm64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1931435/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1931435] Re: crash fails to build on ubuntu 20.10 (Groovy) on arm64

[Ioanna Alifieraki]

Debdiff for G.

** Patch added: "lp1931435_groovy.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1931435/+attachment/5503885/+files/lp1931435_groovy.debdiff

** Tags added: sts-sponsor-ddstreet

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931435

Title:
  crash fails to build on ubuntu 20.10 (Groovy) on arm64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1931435/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL

[Ioanna Alifieraki]

The arm64 build failure on groovy is due to a commit missning regarding
gdb. See bug
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1931435.

On riscv64 it seems it never built successfully and the failure is irrelevant 
to the patch.
See bug https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1931432.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919275

Title:
  crash utility fails on arm64 with  cannot determine VA_BITS_ACTUAL

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1931435] [NEW] crash fails to build on ubuntu 20.10 (Groovy) on arm64

[Ioanna Alifieraki]

Public bug reported:

On arm64, crash fails to build with error "multiple definition of 
`tdesc_aarch64'" [1].
>From upstream git log, seems it can be resolved with commit 
>e770735200c02ac2414c394ea6ec5f7f033efe64 .

[1]
https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu1.20.10.1/+build/21630861

** Affects: crash (Ubuntu)
 Importance: Medium
 Assignee: Ioanna Alifieraki (joalif)
 Status: Confirmed

** Affects: crash (Ubuntu Groovy)
 Importance: Medium
 Assignee: Ioanna Alifieraki (joalif)
 Status: Confirmed

** Changed in: crash (Ubuntu)
   Status: New => Confirmed

** Changed in: crash (Ubuntu)
   Importance: Undecided => Medium

** Changed in: crash (Ubuntu)
 Assignee: (unassigned) => Ioanna Alifieraki (joalif)

** Also affects: crash (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Changed in: crash (Ubuntu Groovy)
   Status: New => Confirmed

** Changed in: crash (Ubuntu Groovy)
   Importance: Undecided => Medium

** Changed in: crash (Ubuntu Groovy)
     Assignee: (unassigned) => Ioanna Alifieraki (joalif)

** Description changed:

- On arm64, crash fails to build with error "multiple definition of 
`tdesc_aarch64'".
+ On arm64, crash fails to build with error "multiple definition of 
`tdesc_aarch64'" [1].
  From upstream git log, seems it can be resolved with commit 
e770735200c02ac2414c394ea6ec5f7f033efe64 .
+ 
+ [1]
+ 
https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu1.20.10.1/+build/21630861

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931435

Title:
  crash fails to build on ubuntu 20.10 (Groovy) on arm64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1931435/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1931435] Re: crash fails to build on ubuntu 20.10 (Groovy) on arm64

[Ioanna Alifieraki]

Currently, working on it. Once I get hands on an arm vm I'll confirm the
fix and make a debdiff.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931435

Title:
  crash fails to build on ubuntu 20.10 (Groovy) on arm64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1931435/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1931432] [NEW] crash FTBFS on riscv64

[Ioanna Alifieraki]

Public bug reported:

Crash fails to build from source on riscv at least for Focal and Groovy,
later releases may also be affected but I haven't confirm it.

Examples of failed builds :

Groovy : 
https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu1.20.10.1/+build/21630864
Focal : 
https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu1.20.04.1/+build/21630885

** Affects: crash (Ubuntu)
 Importance: Medium
 Status: Confirmed

** Affects: crash (Ubuntu Focal)
 Importance: Medium
 Status: Confirmed

** Affects: crash (Ubuntu Groovy)
 Importance: Medium
 Status: Confirmed

** Changed in: crash (Ubuntu)
   Importance: Undecided => Medium

** Changed in: crash (Ubuntu)
   Status: New => Confirmed

** Also affects: crash (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: crash (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: crash (Ubuntu Focal)
   Status: New => Confirmed

** Changed in: crash (Ubuntu Groovy)
   Status: New => Confirmed

** Changed in: crash (Ubuntu Focal)
   Importance: Undecided => Medium

** Changed in: crash (Ubuntu Groovy)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931432

Title:
  crash FTBFS on riscv64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1931432/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1931431] [NEW] crash FTBFS on riscv64

[Ioanna Alifieraki]

Public bug reported:

Crash fails to build from source on riscv at least for Focal and Groovy,
later releases may also be affected but I haven't confirm it.

Examples of failed builds :

Groovy : 
https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu1.20.10.1/+build/21630864
Focal : 
https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu1.20.04.1/+build/21630885

** Affects: crash (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931431

Title:
  crash FTBFS on riscv64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1931431/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL

[Ioanna Alifieraki]

Verification for F and B done. On G build fails, I'll look into it and
update the bug.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919275

Title:
  crash utility fails on arm64 with  cannot determine VA_BITS_ACTUAL

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL

[Ioanna Alifieraki]

#VERIFICATION BIONIC - crash part

Installed crash from -proposed, triggered a crash and opened dump
with crash.
Crash opens dump successfully.

~# crash usr/lib/debug/boot/vmlinux-5.4.0-1049-aws
/var/crash/202106021531/dump.202106021531

crash 7.2.8
Copyright (C) 2002-2020  Red Hat, Inc.

crash> 


** Tags removed: verification-needed-bionic verification-needed-focal
** Tags added: verification-done-bionic verification-done-focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919275

Title:
  crash utility fails on arm64 with  cannot determine VA_BITS_ACTUAL

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL

[Ioanna Alifieraki]

#VERIFICATION FOCAL - crash part

Installed crash from -proposed, triggered a crash and opened dump
with crash.
Crash opens dump successfully.

# crash usr/lib/debug/boot/vmlinux-5.4.0-1049-aws
/var/crash/202106021329/dump.202106021329

crash 7.2.8
Copyright (C) 2002-2020  Red Hat, Inc.

crash>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919275

Title:
  crash utility fails on arm64 with  cannot determine VA_BITS_ACTUAL

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL

[Ioanna Alifieraki]

** Changed in: crash (Ubuntu Bionic)
 Assignee: (unassigned) => Ioanna Alifieraki (joalif)

** Changed in: crash (Ubuntu Focal)
 Assignee: (unassigned) => Ioanna Alifieraki (joalif)

** Changed in: crash (Ubuntu Groovy)
 Assignee: (unassigned) => Ioanna Alifieraki (joalif)

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Ioanna Alifieraki (joalif)

** Changed in: linux (Ubuntu Groovy)
 Assignee: (unassigned) => Ioanna Alifieraki (joalif)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919275

Title:
  crash utility fails on arm64 with  cannot determine VA_BITS_ACTUAL

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL

[Ioanna Alifieraki]

#VERIFICATION GROOVY - kernel part

Installed kernel from -proposed, triggered a crash and opened dump with crash.
Crash opens dump successfully (patched version of crash required with commit 
from description).

# crash usr/lib/debug/boot/vmlinux-5.8.0-1034-aws
/var/crash/202105182030/dump.202105182030

crash 7.2.8
Copyright (C) 2002-2020  Red Hat, Inc.


crash>

** Tags removed: verification-needed-groovy
** Tags added: verification-done-groovy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919275

Title:
  crash utility fails on arm64 with  cannot determine VA_BITS_ACTUAL

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL

[Ioanna Alifieraki]

** Tags removed: verification-needed-focal
** Tags added: verification-done-focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919275

Title:
  crash utility fails on arm64 with  cannot determine VA_BITS_ACTUAL

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL

[Ioanna Alifieraki]

#VERIFICATION FOCAL - kernel part

Installed kernel from -proposed, triggered a crash and opened dump with crash.
Crash opens dump successfully (patched version of crash required with commit 
from description).

# crash usr/lib/debug/boot/vmlinux-5.4.0-1049-aws
/var/crash/202105181907/dump.202105181907

crash 7.2.8
Copyright (C) 2002-2020  Red Hat, Inc.
...

crash>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919275

Title:
  crash utility fails on arm64 with  cannot determine VA_BITS_ACTUAL

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1917780] Re: initramfs-tools does not include fsck binaries in the initrd if all mount pass are 0

[Ioanna Alifieraki]

#VERIFICATION BIONIC

On a bionic machine that has PASSNO set to 0 for all entries,
installed initramfs-tools from -proposed.

# lsinitramfs /boot/initrd.img-5.9.0-rc5+ | grep fsck
sbin/fsck.ext4
sbin/fsck
sbin/e2fsck

fsck utilities are included.

** Tags removed: verification-needed verification-needed-bionic 
verification-needed-focal verification-needed-groovy
** Tags added: verification-done verification-done-bionic 
verification-done-focal verification-done-groovy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917780

Title:
  initramfs-tools does not include fsck binaries in the initrd if all
  mount pass are 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1917780/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1917780] Re: initramfs-tools does not include fsck binaries in the initrd if all mount pass are 0

[Ioanna Alifieraki]

#VERIFICATION GROOVY

On a groovy machine that has PASSNO set to 0 for all entries,
installed initramfs-tools from -proposed.

# lsinitramfs /boot/initrd.img-5.8.0-50-generic | grep fsck
usr/sbin/e2fsck
usr/sbin/fsck
usr/sbin/fsck.ext4

fsck utilities are included.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917780

Title:
  initramfs-tools does not include fsck binaries in the initrd if all
  mount pass are 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1917780/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1917780] Re: initramfs-tools does not include fsck binaries in the initrd if all mount pass are 0

[Ioanna Alifieraki]

#VERIFICATION FOCAL

On a focal machine that has PASSNO set to 0 for all entries,
installed initramfs-tools from -proposed.

# lsinitramfs /boot/initrd.img-5.4.0-72-generic | grep fsck
usr/sbin/e2fsck
usr/sbin/fsck
usr/sbin/fsck.ext4

fsck utilities are included.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917780

Title:
  initramfs-tools does not include fsck binaries in the initrd if all
  mount pass are 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1917780/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922738] Re: 5.4 kernel: when iommu is on crashdump fails

[Ioanna Alifieraki]

VERIFICATION

Installed kernel from -proposed, enabled iommu rebooted and triggered a crash.
Crashdump generated successfully.

** Tags removed: verification-needed-focal
** Tags added: verification-done-focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922738

Title:
  5.4 kernel: when iommu is on crashdump fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922738/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1927519] [NEW] Mitigate libvirt: error : unable to set AppArmor profile 'libvirt-' for '/usr/bin/kvm-spice': No such file or directory

[Ioanna Alifieraki]

Public bug reported:

[Impact]

Some times libvirt fails to start a vm with the following error : 
libvirt:  error : unable to set AppArmor profile 
'libvirt-b05b297f-952f-42d6-b04e-f9a13767db54' for '/usr/bin/kvm-spice': No 
such file or directory

This happens because for some reason file
/etc/apparmor.d/libvirt/libvirt- has 0 size.

Although, we do not now why the above file gets truncated and therefore we do 
not know the root cause, I open this bug to come up with a way to mitigate the 
issue.
E.g. when  libvirt sees that this file is 0-size to delete it and create it 
again.

[Test case]

To reproduce this behaviour, create a vm and stop it, note the uuid.
Then :

## touch /etc/apparmor.d/libvirt/libvirt-
# touch /etc/apparmor.d/libvirt/libvirt-b05b297f-952f-42d6-b04e-f9a13767db54
# ls -la libvirt-b05b297f-952f-42d6-b04e-f9a13767db54
-rw-r--r-- 1 root root 0 May  6 18:46 
libvirt-b05b297f-952f-42d6-b04e-f9a13767db54

Try to start the vm, it will fail with :
libvirt:  error : unable to set AppArmor profile 
'libvirt-b05b297f-952f-42d6-b04e-f9a13767db54' for '/usr/bin/kvm-spice': No 
such file or directory 

To be able to start the vm again just delete the libvirt- file.

[Regression Potential]

TBD

[Other]

Similar reported bug : https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=890084

** Affects: libvirt (Ubuntu)
 Importance: Medium
 Status: Confirmed

** Changed in: libvirt (Ubuntu)
   Importance: Undecided => Medium

** Changed in: libvirt (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927519

Title:
  Mitigate libvirt: error : unable to set AppArmor profile 'libvirt-' for '/usr/bin/kvm-spice': No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1927519/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1926355] Re: Snap applications segfault with new core20 (rev: 1015+)

[Ioanna Alifieraki]

@Balint not sure if you're already aware but the regression caused by LP: 
#1914044 may be causing
the problem in LP: #1867502 .
Earlier today people reported failed deployments with netinstall, autoinstalls 
etc,
which is now working again (I guess because 2.31-0ubuntu9.3 was pulled out of 
-updates).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926355

Title:
  Snap applications segfault with new core20 (rev: 1015+)

To manage notifications about this bug go to:
https://bugs.launchpad.net/snap-core20/+bug/1926355/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1879214] Re: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported

[Ioanna Alifieraki]

#VERIFICATION GROOVY

On an arm64 groovy vm installed makedumpfile from -proposed and triggered a 
crash.
Crashdump file is created without any problems : 

[  192.577224] kdump-tools[528]: Starting kdump-tools:
[  192.579315] kdump-tools[534]:  * running makedumpfile -c -d 31 /proc/vmcore 
/var/crash/202104261101/dump-incomplete
[  OK  ] Started Hostname Service.
Copying data  : [100.0 %] \   eta: 
0s
[  198.320536] kdump-tools[551]: The kernel version is not supported.
[  198.322120] kdump-tools[551]: The makedumpfile operation may be incomplete.
[  198.323793] kdump-tools[551]: The dumpfile is saved to 
/var/crash/202104261101/dump-incomplete.
[  198.325900] kdump-tools[551]: makedumpfile Completed.
[  198.333425] kdump-tools[534]:  * kdump-tools: saved vmcore in 
/var/crash/202104261101
[  198.424133] kdump-tools[534]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/202104261101/dmesg.202104261101
[  198.433298] kdump-tools[555]: The kernel version is not supported.
[  198.434926] kdump-tools[555]: The makedumpfile operation may be incomplete.
[  198.436644] kdump-tools[555]: The dmesg log is saved to 
/var/crash/202104261101/dmesg.202104261101.
[  198.438770] kdump-tools[555]: makedumpfile Completed.
[  198.440651] kdump-tools[534]:  * kdump-tools: saved dmesg content in 
/var/crash/202104261101
[  198.454465] kdump-tools[558]: Mon, 26 Apr 2021 11:01:48 +
[  198.464208] kdump-tools[559]: Rebooting.


** Tags removed: verification-needed verification-needed-bionic 
verification-needed-focal verification-needed-groovy
** Tags added: verification-done verification-done-bionic 
verification-done-focal verification-done-groovy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879214

Title:
  Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to
  makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47
  not supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1879214/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1879214] Re: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported

[Ioanna Alifieraki]

#VERIFICATION FOCAL

On an arm64 focal vm installed makedumpfile from -proposed and triggered a 
crash.
Crashdump file is created without any problems : 

[  131.348948] kdump-tools[521]: Starting kdump-tools:
[  131.350648] kdump-tools[527]:  * running makedumpfile -c -d 31 /proc/vmcore 
/var/crash/202104261059/dump-incomplete
[  OK  ] Started Hostname Service.
Copying data  : [100.0 %] |   eta: 
0s
[  136.780294] kdump-tools[544]: The dumpfile is saved to 
/var/crash/202104261059/dump-incomplete.
[  136.782771] kdump-tools[544]: makedumpfile Completed.
[  136.787843] kdump-tools[527]:  * kdump-tools: saved vmcore in 
/var/crash/202104261059
[  136.909187] kdump-tools[527]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/202104261059/dmesg.202104261059
[  136.917750] kdump-tools[549]: The dmesg log is saved to 
/var/crash/202104261059/dmesg.202104261059.
[  136.919930] kdump-tools[549]: makedumpfile Completed.
[  136.924282] kdump-tools[527]:  * kdump-tools: saved dmesg content in 
/var/crash/202104261059
[  136.938369] kdump-tools[552]: Mon, 26 Apr 2021 11:00:01 +
[  136.947826] kdump-tools[553]: Rebooting.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879214

Title:
  Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to
  makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47
  not supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1879214/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1879214] Re: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported

[Ioanna Alifieraki]

#VERIFICATION BIONIC

On an arm64 bionic vm running 5.4 kernel installed makedumpfile
from -proposed and triggered a crash.
Crashdump file is created without any problems : 

[  130.240270] kdump-tools[632]: Starting kdump-tools:  * running makedumpfile 
-c -d 31 /proc/vmcore /var/crash/202104261056/dump-incomplete
Copying data  : [ 62.6 
[2021-04-26T10:56:38.86529Copying data  : 
[100.0 %] |   eta: 0s
[  143.377037] kdump-tools[632]: The kernel version is not supported.
[  143.378979] kdump-tools[632]: The makedumpfile operation may be incomplete.
[  143.383191] kdump-tools[632]: The dumpfile is saved to 
/var/crash/202104261056/dump-incomplete.
[  143.385712] kdump-tools[632]: makedumpfile Completed.
[  143.388291] kdump-tools[632]:  * kdump-tools: saved vmcore in 
/var/crash/202104261056
[  143.432646] kdump-tools[632]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/202104261056/dmesg.202104261056
[  143.440986] kdump-tools[632]: The kernel version is not supported.
[  143.442600] kdump-tools[632]: The makedumpfile operation may be incomplete.
[  143.444345] kdump-tools[632]: The dmesg log is saved to 
/var/crash/202104261056/dmesg.202104261056.
[  143.446879] kdump-tools[632]: makedumpfile Completed.
[  143.448527] kdump-tools[632]:  * kdump-tools: saved dmesg content in 
/var/crash/202104261056
[  143.463805] kdump-tools[632]: Mon, 26 Apr 2021 10:56:38 +
[  143.473132] kdump-tools[632]: Rebooting.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879214

Title:
  Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to
  makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47
  not supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1879214/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1879214] Re: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported

[Ioanna Alifieraki]

Debdiff for Bionic V2.

** Patch added: "lp1879214_bionic_v2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1879214/+attachment/5488489/+files/lp1879214_bionic_v2.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879214

Title:
  Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to
  makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47
  not supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1879214/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1879214] Re: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported

[Ioanna Alifieraki]

Debdiff for Focal V2.

** Patch added: "lp1879214_focal_v2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1879214/+attachment/5488488/+files/lp1879214_focal_v2.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879214

Title:
  Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to
  makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47
  not supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1879214/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1879214] Re: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported

[Ioanna Alifieraki]

Debdiff for Groovy V2.

** Patch added: "lp1879214_groovy_v2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1879214/+attachment/5488487/+files/lp1879214_groovy_v2.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879214

Title:
  Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to
  makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47
  not supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1879214/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL

[Ioanna Alifieraki]

** Merge proposal linked:
   
https://code.launchpad.net/~joalif/ubuntu/+source/crash/+git/crash/+merge/401229

** Merge proposal linked:
   
https://code.launchpad.net/~joalif/ubuntu/+source/crash/+git/crash/+merge/401230

** Merge proposal linked:
   
https://code.launchpad.net/~joalif/ubuntu/+source/crash/+git/crash/+merge/401231

** Merge proposal linked:
   
https://code.launchpad.net/~joalif/ubuntu/+source/crash/+git/crash/+merge/401232

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919275

Title:
  crash utility fails on arm64 with  cannot determine VA_BITS_ACTUAL

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL

[Ioanna Alifieraki]

** Changed in: crash (Ubuntu Bionic)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919275

Title:
  crash utility fails on arm64 with  cannot determine VA_BITS_ACTUAL

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL

[Ioanna Alifieraki]

** Also affects: crash (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Bionic)
   Status: New => Invalid

** Changed in: crash (Ubuntu Bionic)
   Status: New => Confirmed

** Description changed:

  [Impact]
  
  On Ubuntu Bionic with the 5.4.0-1038-aws kernel the crash utility
  7.2.8-1ubuntu0.18.04 fails with:
  
  crash: cannot determine VA_BITS_ACTUAL
  
  This bug has been addressed upstream and needed patches both in crash
  and kernel.
  
  Kernel patch :
  
  commit bbdbc11804ff0b4130e7550113b452e96a74d16e
  Author: Bhupesh Sharma 
  Date:   Thu May 14 00:22:37 2020 +0530
  arm64/crash_core: Export TCR_EL1.T1SZ in vmcoreinfo
  
  Crash patch :
  
  commit 1c45cea02df7f947b4296c1dcaefa1024235ef10
  Author: Bhupesh Sharma 
  Date:   Tue Jul 14 01:14:49 2020 +0530
  
  arm64: Change tcr_el1_t1sz variable name to TCR_EL1_T1SZ
  
+ 
+ Series affected :
+ 
+ Kenrel : 
+ This affects Focal (5.4 kernel)  and Groovy (5.8 kernel).
+ Hirsute already contains the commit and kernels prior to 5.3 are not affected.
+ 
+ Crash :
+ The commit is already in Hirsute.
+ Groovy, Focal and Bionic are affected.
+ In case of Bionic the bug appears only if 5.4 hwe kernel is used.
+ 
  [Test Case]
  
  On an arm64 host which runs the affected releases and kernels after creating 
a crashdump try to open it with crash.
  It will fail with :
  crash: cannot determine VA_BITS_ACTUAL
  
  [Where problems could occur]
  
  Kernel patch :
  
  The kernel patch reads the appropriate cpu register and exports TCR_EL1.T1SZ 
variable in vmcoreinfo. Given that this is a simple operation
  and that this patch landed upstream in 5.9 and no regressions have been 
reported, it is safe to assume that the regression potential is minimal.
  Any potential problem would occur in vmcoreinfo since this is where 
TCR_EL1.T1SZ variable is exported.
  
  Crash patch :
  
  This patch renames tcr_el1_t1sz variable to TCR_EL1_T1SZ to be compatible 
with the kernel change above for crash to be able to read it.
  The regression potential is small and any problem would regard reading this 
variable.
  
- 
  [Other]
  
  Workaround :
  This bug/change in crash provides a workaround for 5.4+ 
https://github.com/crash-utility/crash/issues/52 kernels.
  
  While it appears as though it this was fixed it
  https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1858958 it still
  doesn't seem to work with a 5.4 kernel including. I also tested
  
https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu0.18.04.1/+build/18807621/+files/crash_7.2.8-1ubuntu0.18.04.1_arm64.deb
  and it exhibits the same problem.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919275

Title:
  crash utility fails on arm64 with  cannot determine VA_BITS_ACTUAL

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL

[Ioanna Alifieraki]

Focal kernel :
Patch submitted 
https://lists.ubuntu.com/archives/kernel-team/2021-April/119287.html

Groovy kernel : 
Patch submitted 
https://lists.ubuntu.com/archives/kernel-team/2021-April/119288.html

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: crash (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: crash (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Changed in: crash (Ubuntu Groovy)
   Status: New => Confirmed

** Changed in: crash (Ubuntu Focal)
   Status: New => Confirmed

** Changed in: linux (Ubuntu Focal)
   Status: New => Confirmed

** Changed in: linux (Ubuntu Groovy)
   Status: New => Confirmed

** Changed in: linux (Ubuntu Groovy)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Focal)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Changed in: crash (Ubuntu Groovy)
   Importance: Undecided => Medium

** Changed in: crash (Ubuntu Focal)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919275

Title:
  crash utility fails on arm64 with  cannot determine VA_BITS_ACTUAL

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL

[Ioanna Alifieraki]

** Also affects: crash-installer
   Importance: Undecided
   Status: New

** No longer affects: crash-installer

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919275

Title:
  crash utility fails on arm64 with  cannot determine VA_BITS_ACTUAL

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL

[Ioanna Alifieraki]

** Description changed:

  [Impact]
  
  On Ubuntu Bionic with the 5.4.0-1038-aws kernel the crash utility
  7.2.8-1ubuntu0.18.04 fails with:
  
  crash: cannot determine VA_BITS_ACTUAL
  
  This bug has been addressed upstream and needed patches both in crash
  and kernel.
  
  Kernel patch :
  
  commit bbdbc11804ff0b4130e7550113b452e96a74d16e
  Author: Bhupesh Sharma 
  Date:   Thu May 14 00:22:37 2020 +0530
- arm64/crash_core: Export TCR_EL1.T1SZ in vmcoreinfo
- 
+ arm64/crash_core: Export TCR_EL1.T1SZ in vmcoreinfo
  
  Crash patch :
  
  commit 1c45cea02df7f947b4296c1dcaefa1024235ef10
  Author: Bhupesh Sharma 
  Date:   Tue Jul 14 01:14:49 2020 +0530
  
- arm64: Change tcr_el1_t1sz variable name to TCR_EL1_T1SZ
- 
+ arm64: Change tcr_el1_t1sz variable name to TCR_EL1_T1SZ
  
  [Test Case]
  
  On an arm64 host which runs the affected releases and kernels after creating 
a crashdump try to open it with crash.
  It will fail with :
  crash: cannot determine VA_BITS_ACTUAL
  
+ [Where problems could occur]
  
- [Where problems could occur]
+ Kernel patch :
+ 
+ The kernel patch reads the appropriate cpu register and exports TCR_EL1.T1SZ 
variable in vmcoreinfo. Given that this is a simple operation
+ and that this patch landed upstream in 5.9 and no regressions have been 
reported, it is safe to assume that the regression potential is minimal.
+ Any potential problem would occur in vmcoreinfo since this is where 
TCR_EL1.T1SZ variable is exported.
+ 
+ Crash patch :
+ 
+ This patch renames tcr_el1_t1sz variable to TCR_EL1_T1SZ to be compatible 
with the kernel change above for crash to be able to read it.
+ The regression potential is small and any problem would regard reading this 
variable.
+ 
  
  [Other]
  
  Workaround :
  This bug/change in crash provides a workaround for 5.4+ 
https://github.com/crash-utility/crash/issues/52 kernels.
  
  While it appears as though it this was fixed it
  https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1858958 it still
  doesn't seem to work with a 5.4 kernel including. I also tested
  
https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu0.18.04.1/+build/18807621/+files/crash_7.2.8-1ubuntu0.18.04.1_arm64.deb
  and it exhibits the same problem.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919275

Title:
  crash utility fails on arm64 with  cannot determine VA_BITS_ACTUAL

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL

[Ioanna Alifieraki]

** Description changed:

+ [Impact]
+ 
  On Ubuntu Bionic with the 5.4.0-1038-aws kernel the crash utility
  7.2.8-1ubuntu0.18.04 fails with:
  
  crash: cannot determine VA_BITS_ACTUAL
  
- This bug/change in crash provides a workaround for 5.4+
- https://github.com/crash-utility/crash/issues/52 kernels.
+ This bug has been addressed upstream and needed patches both in crash
+ and kernel.
+ 
+ Kernel patch :
+ 
+ commit bbdbc11804ff0b4130e7550113b452e96a74d16e
+ Author: Bhupesh Sharma 
+ Date:   Thu May 14 00:22:37 2020 +0530
+ arm64/crash_core: Export TCR_EL1.T1SZ in vmcoreinfo
+ 
+ 
+ Crash patch :
+ 
+ commit 1c45cea02df7f947b4296c1dcaefa1024235ef10
+ Author: Bhupesh Sharma 
+ Date:   Tue Jul 14 01:14:49 2020 +0530
+ 
+ arm64: Change tcr_el1_t1sz variable name to TCR_EL1_T1SZ
+ 
+ 
+ [Test Case]
+ 
+ On an arm64 host which runs the affected releases and kernels after creating 
a crashdump try to open it with crash.
+ It will fail with :
+ crash: cannot determine VA_BITS_ACTUAL
+ 
+ 
+ [Where problems could occur]
+ 
+ [Other]
+ 
+ Workaround :
+ This bug/change in crash provides a workaround for 5.4+ 
https://github.com/crash-utility/crash/issues/52 kernels.
  
  While it appears as though it this was fixed it
  https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1858958 it still
  doesn't seem to work with a 5.4 kernel including. I also tested
  
https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu0.18.04.1/+build/18807621/+files/crash_7.2.8-1ubuntu0.18.04.1_arm64.deb
  and it exhibits the same problem.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919275

Title:
  crash utility fails on arm64 with  cannot determine VA_BITS_ACTUAL

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL

[Ioanna Alifieraki]

** Changed in: crash (Ubuntu)
 Assignee: (unassigned) => Ioanna Alifieraki (joalif)

** Changed in: crash (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919275

Title:
  crash utility fails on arm64 with  cannot determine VA_BITS_ACTUAL

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1879214] Re: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported

[Ioanna Alifieraki]

Debdiff for Bionic.

** Patch added: "lp1879214_bionic.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1879214/+attachment/5487329/+files/lp1879214_bionic.debdiff

** Also affects: makedumpfile (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: makedumpfile (Ubuntu Bionic)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879214

Title:
  Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to
  makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47
  not supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1879214/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1879214] Re: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported

[Ioanna Alifieraki]

This bug also affects Bionic when 5.4 hwe kernel is used.

** Description changed:

  [Impact]
  
  On arm64 and kernels 5.4+ makedumpfile fails.
  
  Upstream patches solve this bug :
  
  [PATCH 1/3] Use vmcoreinfo note in /proc/kcore for --mem-usage option
  
https://github.com/makedumpfile/makedumpfile/commit/d8b701796f0491f2ac4b06c7a5b795c29399efab
  
  [PATCH 2/3] arm64: Make use of NUMBER(VA_BITS) in vmcoreinfo
  
https://github.com/makedumpfile/makedumpfile/commit/67d0e1d68f28c567a704fd6b9b8fd696ad3df183
  
  [PATCH 3/3] arm64: support flipped VA and 52-bit kernel VA
  
https://github.com/makedumpfile/makedumpfile/commit/a0216b678a95f099a16172cc4a67ad5aa6a89583
  
  [Test Case]
  
  OS: Ubuntu 20.04 LTS
  kernel: 5.4.0-21-generic
  arch:arm64
  Description:
  When testing kdump on Ubuntu 20.04 LTS (arm64), makedumpfile fails. The test 
steps are as follows:
  # echo 1> / proc / sys / kernel / sysrq
  # echo c> / proc / sysrq-trigger
  The error logs are as follows:
  [   26.599161] kdump-tools[653]: Starting kdump-tools:
  [   26.612761] kdump-tools[659]: Starting kdump-tools:
  [   26.628565] kdump-tools[659]: * running makedumpfile -c -d 31 /proc/vmcore 
/var/crash/2020050
  [   26.648621] kdump-tools[676]: * running makedumpfile -c -d 31 /proc/vmcore 
/var/crash/2020050
  [   26.668445] kdump-tools[676]: calculate_plat_config: PAGE SIZE 0x1000 and 
VA Bits 47 not supported
  [   26.678199] kdump-tools[676]: get_machdep_info_arm64
  [   26.692518] kdump-tools[659]: get_machdep_info_arm64
  [   26.852221] hns3 :7d:00.0: get link status cmd failed -16
  
  [   94.351303] kdump-tools[659]: * kdump-tools: makedumpfile failed, * 
kdump-tools: saved vmcore in /var/crash/202005061048
  [   94.435510] kdump-tools[659]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/202005061048/dmesg.202005061048
  [   94.457103] kdump-tools[688]: calculate_plat_config: PAGE SIZE 0x1000 and 
VA Bits 47 not supported
  [   94.476228] kdump-tools[688]: get_machdep_info_arm64: Can't determine 
platform config values
  [   94.485912] kdump-tools[688]: makedumpfile Failed.
  [   94.500760] kdump-tools[659]:  * kdump-tools: makedumpfile --dump-dmesg 
failed. dmesg content will be unavailable
  [   94.520225] kdump-tools[659]:  * kdump-tools: failed to save dmesg content 
in /var/crash/202005061048
  [   94.544205] kdump-tools[691]: Wed, 06 May 2020 10:49:42 -0400
  [   94.564597] kdump-tools[692]: Rebooting.
  [   94.678709] reboot: Restarting systemlpc uart init Done
  
  [Regression Potential]
  
  Patch 1 : [PATCH 1/3] Use vmcoreinfo note in /proc/kcore for --mem-usage 
option
  removes get_elf_loads function this function was only used with --mem-usage 
option
  , since kernel commit kernel commit 23c85094fe18 (kernel versions >4.19)
  the information needed is in vmcoreinfo
  Any regression potential would affect the --mem-usage only
  
  Patch 2 : [PATCH 2/3] arm64: Make use of NUMBER(VA_BITS) in vmcoreinfo
  arm64 only
  make use of NUMBER(VA_BITS) in vmcoreinfo as the current way of guessing 
VA_BITS
  does not work on Linux 5.4 and later.
  Before this commit VA_BITS would be calculated in get_versiondep_info_arm64, 
however
  this way of calculation breaks after 5.4. This commit gets the VA_BITS from 
vmcoreinfo
  and as a safeguard it uses the old way of deriving VA_BITS only if reading 
from vmcoreinfo doesn't work.
  
  From the kernel side VA_BITS is in vmcoreinfo since kernel 4.12, F and later 
use later kernel so not
  great regression potentional and if any it would only affect arm64.
  
  Patch 3 : [PATCH 3/3] arm64: support flipped VA and 52-bit kernel VA
  arm64 only
  Linux 5.4 and later kernels for arm64 changed the kernel VA space
  arrangement and introduced 52-bit kernel VAs by merging branch
  commit b333b0ba2346.  Support 5.9+ kernels with vmcoreinfo entries
  and 5.4+ kernels with best guessing.
  
  This patch makes adjustemnt to properly calculate vabits_actual, 
max_physmem_bits, page_offset
  Any regression potential would affect only arm64 and the calculation of the 
above variables.
  
  [Other]
  
  For H only the 3 commits are needed and they cherry-pick.
  
  For G and F the 3rd commit does not apply and an extra commit is needed
  :
  
  commit da0d25ffa585c9a1adb94562c815daa393b1ee5e
  [PATCH] arm64: Add support for ARMv8.2-LPA (52-bit PA support)
+ 
+ This bug also affects Bionic when 5.4 hwe kernel is used.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879214

Title:
  Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to
  makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47
  not supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1879214/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1879214] Re: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported

[Ioanna Alifieraki]

** Bug watch added: Debian Bug tracker #986594
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986594

** Also affects: makedumpfile (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986594
   Importance: Unknown
   Status: Unknown

** Changed in: makedumpfile (Ubuntu Groovy)
 Assignee: (unassigned) => Ioanna Alifieraki (joalif)

** Changed in: makedumpfile (Ubuntu Focal)
 Assignee: (unassigned) => Ioanna Alifieraki (joalif)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879214

Title:
  Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to
  makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47
  not supported

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1879214/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921403] Re: makedumpfile does not create dmesg file in /var/crash on 5.10+ kernels

[Ioanna Alifieraki]

** Changed in: makedumpfile (Ubuntu Hirsute)
 Assignee: (unassigned) => Ioanna Alifieraki (joalif)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921403

Title:
  makedumpfile does not create dmesg file in /var/crash on 5.10+ kernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1921403/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922738] Re: 5.4 kernel: when iommu is on crashdump fails

[Ioanna Alifieraki]

** Description changed:

  [IMPACT]
  
  When iommu is enabled crashdump fails to be collected because crash-kernel 
crashes
  with following trace [1].
  
  Commits that address it :
  
  1ddb32da4a62 iommu/vt-d: Simplify check in identity_mapping()
  96d170f3b1a6 iommu/vt-d: Remove deferred_attach_domain()
  a11bfde9c77d iommu/vt-d: Do deferred attachment in iommu_need_mapping()
  034d98cc0cdc iommu/vt-d: Move deferred device attachment into helper function
  1d4615978f52 iommu/vt-d: Add attach_deferred() helper
  1ee0186b9a12 iommu/vt-d: Refactor find_domain() helper
  
  [TEST CASE]
  
  Install a 5.4 kernel, add intel_iommu=on and iommu=pt to grub cmdline
  and trigger a crash.
  The crash kernel that boots will crash with trace [1].
  
  [REGRESSION POTENTIAL]
  
+ 1) 1ee0186b9a12 iommu/vt-d: Refactor find_domain() helper
+ Refactors find_domain() into two helpers: 1) find_domain()
+ only returns the domain in use; 2) deferred_attach_domain() does
+ the deferred domain attachment if required and return the domain
+ in use.
+ 
+ 2) 1d4615978f52 iommu/vt-d: Add attach_deferred() helper
+ Add helper function to check if a device's attach process is deffered.
+ Before this commit, this check was done with "dev->archdata.iommu == 
DEFER_DEVICE_DOMAIN_INFO".
+ This commit wraps it into a function.
+ Fixes (1).
+ 
+ 3) 034d98cc0cdc iommu/vt-d: Move deferred device attachment into helper 
function
+ Takes the code that does the deffered attachment from 
deferred_attach_domain() function
+ and places it in new do_deferred_attach() function.
+ Fixes (1).
+ 
+ 4) a11bfde9c77d iommu/vt-d: Do deferred attachment in iommu_need_mapping()
+ This one actually fixes the bug.
+ Attachement of devive needs to happen before checking if device is identity 
mapped.
+ Fixes (1).
+ 
+ 5) 96d170f3b1a6 iommu/vt-d: Remove deferred_attach_domain()
+ Code cleanup, removes deferred_attach_domain() which now is just a wrapper 
around
+ find_domain and calls directly find_domain from caller sites.
+ Fixes (1).
+ 
+ 6) 1ddb32da4a62 iommu/vt-d: Simplify check in identity_mapping()
+ Code cleanup.
+ Fixes (1).
+ 
+ Commits 2,3,5, and 6 are code movements/cleanups so little regression 
potential.
+ Commit 1 is the intial code refactroring ( the rest of commits fix it) and 
commit
+ 3 fixes the bug.
+ 
+ So far testing has not revealed any regression. Any possible regression will 
regard 
+ device deffered attachment.
+ 
  [OTHER]
  
  Kernel affected 5.4.
  
  [1] https://pastebin.ubuntu.com/p/FNxTxjg3DV/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922738

Title:
  5.4 kernel: when iommu is on crashdump fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922738/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922738] [NEW] 5.4 kernel: when iommu is on crashdump fails

[Ioanna Alifieraki]

Public bug reported:

[IMPACT]

When iommu is enabled crashdump fails to be collected because crash-kernel 
crashes
with following trace [1].

Commits that address it :

1ddb32da4a62 iommu/vt-d: Simplify check in identity_mapping()
96d170f3b1a6 iommu/vt-d: Remove deferred_attach_domain()
a11bfde9c77d iommu/vt-d: Do deferred attachment in iommu_need_mapping()
034d98cc0cdc iommu/vt-d: Move deferred device attachment into helper function
1d4615978f52 iommu/vt-d: Add attach_deferred() helper
1ee0186b9a12 iommu/vt-d: Refactor find_domain() helper

[TEST CASE]

Install a 5.4 kernel, add intel_iommu=on and iommu=pt to grub cmdline
and trigger a crash.
The crash kernel that boots will crash with trace [1].

[REGRESSION POTENTIAL]

[OTHER]

Kernel affected 5.4.

[1] https://pastebin.ubuntu.com/p/FNxTxjg3DV/

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete

** Affects: linux (Ubuntu Focal)
 Importance: Medium
 Assignee: Ioanna Alifieraki (joalif)
 Status: Confirmed

** Also affects: linux (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Focal)
   Status: New => Confirmed

** Changed in: linux (Ubuntu Focal)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Focal)
 Assignee: (unassigned) => Ioanna Alifieraki (joalif)

** Description changed:

+ [IMPACT]
+ 
  When iommu is enabled crashdump fails to be collected because crash-kernel 
crashes
- with following trace [1]. 
+ with following trace [1].
  
  Commits that address it :
  
  1ddb32da4a62 iommu/vt-d: Simplify check in identity_mapping()
  96d170f3b1a6 iommu/vt-d: Remove deferred_attach_domain()
- a11bfde9c77d iommu/vt-d: Do deferred attachment in iommu_need_mapping() 
+ a11bfde9c77d iommu/vt-d: Do deferred attachment in iommu_need_mapping()
  034d98cc0cdc iommu/vt-d: Move deferred device attachment into helper function
  1d4615978f52 iommu/vt-d: Add attach_deferred() helper
  1ee0186b9a12 iommu/vt-d: Refactor find_domain() helper
  
+ [TEST CASE]
+ 
+ Install a 5.4 kernel, add intel_iommu=on and iommu=pt to grub cmdline
+ and trigger a crash.
+ The crash kernel that boots will crash with trace [1].
+ 
+ [REGRESSION POTENTIAL]
+ 
+ [OTHER]
+ 
  Kernel affected 5.4.
  
  [1] https://pastebin.ubuntu.com/p/FNxTxjg3DV/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922738

Title:
  5.4 kernel: when iommu is on crashdump fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922738/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921403] Re: makedumpfile does not create dmesg file in /var/crash on 5.10+ kernels

[Ioanna Alifieraki]

** Bug watch added: Debian Bug tracker #985896
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985896

** Also affects: makedumpfile (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985896
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921403

Title:
  makedumpfile does not create dmesg file in /var/crash on 5.10+ kernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1921403/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1921403] [NEW] makedumpfile does not create dmesg file in /var/crash on 5.10+ kernels

[Ioanna Alifieraki]

Public bug reported:

makedumpfile does not create the dmesg. in /var/crash.
This happens only on 5.10+ kernel because 5.10 kernel introduces a new
lockless ringbuffer.

This issue has been addressed upstream with commits :
[1] c617ec633392([PATCH 1/2] printk: add support for lockless ringbuffer)
[2] 44b073b7ec46([PATCH 2/2] printk: use committed/finalized state values)

[1] 
https://github.com/makedumpfile/makedumpfile/commit/c617ec63339222f3a44d73e36677a9acc8954ccd
[2] 
https://github.com/makedumpfile/makedumpfile/commit/44b073b7ec467aee0d7de381d455b8ace1199184

** Affects: makedumpfile (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: makedumpfile (Ubuntu Hirsute)
 Importance: Undecided
 Status: New

** Affects: makedumpfile (Debian)
 Importance: Unknown
 Status: Unknown

** Also affects: makedumpfile (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921403

Title:
  makedumpfile does not create dmesg file in /var/crash on 5.10+ kernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1921403/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs