forked from pool/kdump
Update upstream status for patches by michals
OBS-URL: https://build.opensuse.org/package/show/Kernel:kdump/kdump?expand=0&rev=132
This commit is contained in:
parent
0e3d6319a6
commit
bbbbb70cc7
@ -1,5 +1,9 @@
|
||||
From: Michal Suchanek <msuchanek@suse.de>
|
||||
Date: Wed Jun 21 15:31:21 2017 +0200
|
||||
Subject: Do not request filesystem check on bind mounts
|
||||
References: bsc#1034169
|
||||
Upstream: v0.8.17
|
||||
Git-commit: 395a14377816a19678da481cafdf2332e0b0c932
|
||||
|
||||
When creating fstab for kdump bind mounts the dump and fsck fields are not
|
||||
specified. These should be 0 because the directory which is bind-mounted cannot
|
||||
|
@ -1,5 +1,9 @@
|
||||
From: Michal Suchanek <msuchanek@suse.de>
|
||||
Date: Wed Jun 21 15:25:49 2017 +0200
|
||||
Subject: Do not free fadump memory when reboot is requested
|
||||
References: bsc#1040610
|
||||
Upstream: v0.8.17
|
||||
Git-commit: 653f8c0931c638cbb0bd5c22fc0e1dfd7969b29a
|
||||
|
||||
Freeing fadump memory can take a long time and doing it when we are going to
|
||||
reboot anyway is pointless.
|
||||
|
@ -1,5 +1,9 @@
|
||||
From: Michal Suchanek <msuchanek@suse.de>
|
||||
Date: Wed Jun 21 15:23:30 2017 +0200
|
||||
Subject: Remount /sysroot readwrite when used for kdump
|
||||
References: bsc#1034169
|
||||
Upstream: v0.8.17
|
||||
Git-commit: b3e40e6cb5794e441ddabf1de88f3729ebd0cc6f
|
||||
|
||||
When kdump is saved to / (ie /var is not separate filesystem) /kdump/mnt0 is
|
||||
bind mount of readonly /sysroot. Due to mount bug "mount /kdump/mnt0 -o
|
||||
|
@ -1,5 +1,9 @@
|
||||
From: Michal Suchanek <msuchanek@suse.de>
|
||||
Date: Wed Jun 21 15:33:01 2017 +0200
|
||||
Subject: Source save_dump.sh in systemd service.
|
||||
References: bcs#1034169
|
||||
Upstream: v0.8.17
|
||||
Git-commit: b053165dd633978b1a78f6f7f993d34a62ee97c3
|
||||
|
||||
save_dump.sh is designed to be sourced and contains a number of toplevel return
|
||||
statements. Bash will complain when these are executed unless the script is
|
||||
|
Loading…
Reference in New Issue
Block a user