Ubuntu
zfcpdump-kernel package

  1. Bug #1877089
  2. Comment #3

Comment 3 for bug 1877089

Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2020-05-06 08:28 EDT-------
(In reply to comment #6)
> We can either revert the path change in s390-tools or rebuild the zfcpdump
> kernel flavour with the new name.

This should IMO be decided by the s390tools maintainer! (I personally prefer the latter.)

------- Comment From <email address hidden> 2020-05-06 08:34 EDT-------
(In reply to comment #7)
> Separately, are you expecting for the zfcpdump-kernel to be secure boot
> signed? because currently it is not.

Yes: If a user has booted his system with Secure Boot enables and needs to perform a standalone zfcp dump, the HMC panel keeps the setting of Secure Boot enablement. Thus, if it was enabled for normal zfcp boot, it remains enabled for zfcp dump, and if the zfcpdump kernel is not signed, the dump fails and probably part of the memory content is lost. Secondly, if dumpconf is being used, the automatic zfcpdump will fail, too.