kdumpctl: Error out in case there are white spaces before an option name
Resolves: BZ1484945 https://bugzilla.redhat.com/show_bug.cgi?id=1484945 Currently the kdumpctl script doesn't handle whitespaces (including TABs) which might be there before an option name in the kdump.conf This patch addresses this issue, by ensuring that the kdumpctl errors out in case it finds any stray space(s) or tab(s) before a option name. Reported-by: Kenneth D'souza <kdsouza@redhat.com> Signed-off-by: Bhupesh Sharma <bhsharma@redhat.com> Acked-by: Pratyush Anand <panand@redhat.com> Acked-by: Dave Young <dyoung@redhat.com>
This commit is contained in:
parent
4594c9830d
commit
cb3d1c1c3f
7
kdumpctl
7
kdumpctl
@ -364,6 +364,13 @@ check_config()
|
||||
return 1
|
||||
}
|
||||
|
||||
# Check if we have any leading spaces (or tabs) before the
|
||||
# variable name in the kdump conf file
|
||||
if grep -E -q '^[[:blank:]]+[a-z]' $KDUMP_CONFIG_FILE; then
|
||||
echo "No whitespaces are allowed before a kdump option name in $KDUMP_CONFIG_FILE"
|
||||
return 1
|
||||
fi
|
||||
|
||||
while read config_opt config_val; do
|
||||
case "$config_opt" in
|
||||
\#* | "")
|
||||
|
Loading…
Reference in New Issue
Block a user