Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-3354

fix: retry read of kexec_crash_size

    • rhel-system-roles-1.23.0-2.1.el8
    • None
    • None
    • rhel-sst-system-roles
    • 11
    • 12
    • None
    • QE ack, Dev ack
    • False
    • Hide

      None

      Show
      None
    • Yes
    • Red Hat Enterprise Linux
    • None
    • Bug Fix
    • Hide
      .The Kdump system role works correctly when the kexec_crash_size file is busy

      The `/sys/kernel/kexec_crash_size` file provides the size of the memory region allocated for crash kernel memory.

      Previously, the Kdump system role failed when the `/sys/kernel/kexec_crash_size` file was busy. With this update, the system role retries reading the file when it is available. As a result, the system role no longer fails when the file is busy.
      Show
      .The Kdump system role works correctly when the kexec_crash_size file is busy The `/sys/kernel/kexec_crash_size` file provides the size of the memory region allocated for crash kernel memory. Previously, the Kdump system role failed when the `/sys/kernel/kexec_crash_size` file was busy. With this update, the system role retries reading the file when it is available. As a result, the system role no longer fails when the file is busy.
    • Done
    • None

      Cause: Reading /sys/kernel/kexec_crash_size can report errno 16 - device busy.

      Consequence: The role fails because it cannot read the value.

      Fix: Retry the read.

      Result: The role does not fail if /sys/kernel/kexec_crash_size is busy.

      Signed-off-by: Rich Megginson <rmeggins@redhat.com>

              rmeggins@redhat.com Richard Megginson
              rmeggins@redhat.com Richard Megginson
              Richard Megginson Richard Megginson
              David Jez David Jez
              Marek Suchánek Marek Suchánek (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: