From: Dimitri John Ledkov <xnox@ubuntu.com>
To: linux-s390@vger.kernel.org
Cc: Dimitri John Ledkov <xnox@ubuntu.com>, stable@vger.kernel.org
Subject: [PATCH] s390: fix zfcpdump_defconfig failing to perform zfcpdump
Date: Thu, 12 Oct 2017 11:37:26 +0100 [thread overview]
Message-ID: <1507804646-6197-1-git-send-email-xnox@ubuntu.com> (raw)
zipl from s390-tools generates root=/dev/ram0 kernel cmdline for
zfcpdump, thus BLK_DEV_RAM is required.
zfcpdump initrd mounts DEBUG_FS, thus it is also required.
Without above two options kernel images built with zfcpdump_defconfig
fail to perform zfcpdump. Affects v4.10+.
Bug-Ubuntu: https://launchpad.net/bugs/1722735
Bug-Ubuntu: https://launchpad.net/bugs/1719290
Cc: stable@vger.kernel.org
Signed-off-by: Dimitri John Ledkov <xnox@ubuntu.com>
---
arch/s390/configs/zfcpdump_defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/s390/configs/zfcpdump_defconfig b/arch/s390/configs/zfcpdump_defconfig
index afa46a7..04e042e 100644
--- a/arch/s390/configs/zfcpdump_defconfig
+++ b/arch/s390/configs/zfcpdump_defconfig
@@ -27,6 +27,7 @@ CONFIG_NET=y
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
CONFIG_DEVTMPFS=y
# CONFIG_FIRMWARE_IN_KERNEL is not set
+CONFIG_BLK_DEV_RAM=y
# CONFIG_BLK_DEV_XPRAM is not set
# CONFIG_DCSSBLK is not set
# CONFIG_DASD is not set
@@ -59,6 +60,7 @@ CONFIG_CONFIGFS_FS=y
# CONFIG_NETWORK_FILESYSTEMS is not set
CONFIG_PRINTK_TIME=y
CONFIG_DEBUG_INFO=y
+CONFIG_DEBUG_FS=y
CONFIG_DEBUG_KERNEL=y
CONFIG_PANIC_ON_OOPS=y
# CONFIG_SCHED_DEBUG is not set
--
2.7.4
next reply other threads:[~2017-10-12 10:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 10:37 Dimitri John Ledkov [this message]
2017-10-13 8:28 ` [PATCH] s390: fix zfcpdump_defconfig failing to perform zfcpdump Michael Holzheu
2017-10-13 13:36 ` Dimitri John Ledkov
2017-10-16 9:24 ` Michael Holzheu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1507804646-6197-1-git-send-email-xnox@ubuntu.com \
--to=xnox@ubuntu.com \
--cc=linux-s390@vger.kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox