UBUNTU: [Packaging] switch to triggers for postinst.d postrm.d handling
When we install linux-image we have to run kernel postinst.d support in
case this kernel has no linux-image-extra. Should it have an extra and
we install we then have to assume that is being installed cold
and that the same processing is neeed. If we are installing both at the
same time, we necessarily trigger kernel postinst.d twice. As this
includes rebuilding the initramfs and reconfiguring the boot loader this
is very inefficient.
For removal of linux-image-extra when we remove the package we also
need to run postinst.d handling in order to pare down the initramfs to
linux-image contents only. However when we are removing both packages
we immediatly remove the rebuilt initramfs. Doubly annoying.
This patch switches us to using a trigger against the linux-image package
for all postinst.d and postrm.d handling. On installation postinst.d
gets triggered twice once by linux-image and once by linux-image-extra.
As triggers are non-cumulative we will only run this processing
once. When removing both packages we will trigger postinst.d from
linux-image-extra and then in linux-image postrm.d we effectivly ignore
the pending trigger and simply run the postrm.d. This prevents us from
rebuilding the initramfs.
UBUNTU: SAUCE: apparmor: fix memory leak when duplicate profile load
AppArmor is leaking the newly loaded profile and its proxy when
the profile is an exact match to the currently loaded version.
In this case the match check results in the profile being skipped
and put with out dealing with the proxy and forwarding thus creating
a circular refcount and a leak.
On some boards, under heavy load, the EC firmware is
unable to complete commands even in one second. Increasing
the command completion timeout value to five seconds.
Fixes: c1b0bc2dabfa ("usb: typec: Add support for UCSI interface")
Cc: <email address hidden>
Signed-off-by: Heikki Krogerus <email address hidden>
Signed-off-by: Thadeu Lima de Souza Cascardo <email address hidden>
Acked-by: Seth Forshee <email address hidden>
Acked-by: Colin King <email address hidden>
Acked-by: Stefan Bader <email address hidden>
When setting up a CPU, we "push" (activate) a pool VP for it.
However it's an error to do so if it already has an active
pool VP.
This happens when doing soft CPU hotplug on powernv since we
don't tear down the CPU on unplug. The HW flags the error which
gets captured by the diagnostics.
Fix this by making sure to "pull" out any already active pool
first.
