> AFAIK you are the only official distribution that uses 4.13 for zfcpdump - 
> therefore IMHO this should be sufficient.
That is not true. We do not use v4.13 kernel for zfcpdump-kernel package. 
zfcpdump-kernel package is based on v4.9 and upgrading that to v4.10+ fails to 
perform any dumps at all.

Please see https://bugs.launchpad.net/ubuntu/+source/zfcpdump-
kernel/+bug/1722735 which has been requested for reverse-proxy.

Why was debugfs disabled upstream? Especially since s390-tools
explicitly tries to mount debugfs.

** Changed in: ubuntu-z-systems
       Status: Incomplete => Confirmed

** No longer affects: linux-hwe (Ubuntu)

** No longer affects: zfcpdump-kernel (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1719290

Title:
  CONFIG_DEBUG_FS is not enabled by "make zfcpdump_defconfig" with
  Ubuntu 17.10 (kernel 4.13)

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu 17.10 uses kernel 4.13.

  We just found out that on this kernel version CONFIG_DEBUG_FS is not
  enabled by "make zfcpdump_defconfig".

  This makes zfcpdump fail with the following error message:

  ERROR: Unable to mount debugfs 
  No such file or directory

  Patch solving this problem is attached

  As reference following bugzilla
  As reference h
  IBM bugzilla for enabling zfcpdump: 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=139974

  or Launchpad 
  https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1565841

  == Comment: #1 - Heinz-Werner Seeck <heinz-werner_se...@de.ibm.com> -
  2017-09-25 06:00:23 ==

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1719290/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to