From: Jose Ignacio Tornos Martinez <jtornosm@redhat.com>
To: masahiroy@kernel.org
Cc: dcavalca@meta.com, jtornosm@redhat.com,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
nathan@kernel.org, ndesaulniers@google.com, nicolas@fjasle.eu,
stable@vger.kernel.org
Subject: Re: [PATCH V5 2/2] rpm-pkg: avoid install/remove the running kernel
Date: Thu, 18 Jan 2024 15:12:45 +0100 [thread overview]
Message-ID: <20240118141246.370272-1-jtornosm@redhat.com> (raw)
In-Reply-To: <CAK7LNARX==sMKVTGXutGMmMkfg1idGUYLhBLZvKZ0psdwmiUvQ@mail.gmail.com>
> What is the problem with this?
In my opinion, it is risky to remove the kernel that is running, that is
the reason why I am trying to protect this.
If you try to remove or update (and the running kernel is removed), if the
kernel and modules are already preloaded in memory, it could not happen
anything but some extra action could be necessary or automatically started,
and even the new kernel could not boot.
Fedora and others are taking this into account with upper tools and declare
the running kernel as protected avoinding this action. But others
(i.e. openSUSE Tumbleweed) allow this behavior.
It may only be a safety measure but it can also be beneficial to avoid
problems, just in case.
Besides, in this way, all the tested distributions would have the same
behavior.
If it is ok, I will create a following version patch describing the problem
better and using indentation as you suggested for the other patch.
Thanks
Best regards
José Ignacio
next prev parent reply other threads:[~2024-01-18 14:12 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 23:33 [PATCH] rpm-pkg: simplify installkernel %post Davide Cavalca via B4 Relay
2023-11-08 0:07 ` Nathan Chancellor
2023-12-12 17:10 ` [PATCH v2] " Jose Ignacio Tornos Martinez
2023-12-12 19:19 ` Nathan Chancellor
2023-12-18 18:26 ` Masahiro Yamada
2023-12-19 8:43 ` Jose Ignacio Tornos Martinez
2023-12-19 15:56 ` [PATCH v3] " Jose Ignacio Tornos Martinez
2023-12-19 16:49 ` Masahiro Yamada
2023-12-19 20:17 ` [PATCH v4] " Jose Ignacio Tornos Martinez
2023-12-20 17:18 ` Nathan Chancellor
2023-12-26 4:02 ` Masahiro Yamada
2024-01-07 15:25 ` Jose Ignacio Tornos Martinez
2024-01-14 8:06 ` [PATCH V5 1/2] " Jose Ignacio Tornos Martinez
2024-01-17 1:29 ` Masahiro Yamada
2024-01-18 14:12 ` Jose Ignacio Tornos Martinez
2024-01-21 17:32 ` Masahiro Yamada
2024-01-22 18:22 ` Jose Ignacio Tornos Martinez
2024-01-22 18:22 ` [PATCH] " Jose Ignacio Tornos Martinez
2024-01-28 7:32 ` Masahiro Yamada
2024-01-29 9:27 ` Jose Ignacio Tornos Martinez
2024-01-29 9:28 ` [PATCH v7] " Jose Ignacio Tornos Martinez
2024-01-31 1:48 ` Masahiro Yamada
2024-01-14 8:07 ` [PATCH V5 2/2] rpm-pkg: avoid install/remove the running kernel Jose Ignacio Tornos Martinez
2024-01-17 1:32 ` Masahiro Yamada
2024-01-18 14:12 ` Jose Ignacio Tornos Martinez [this message]
2024-01-21 17:33 ` Masahiro Yamada
2024-01-22 15:53 ` Jose Ignacio Tornos Martinez
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=20240118141246.370272-1-jtornosm@redhat.com \
--to=jtornosm@redhat.com \
--cc=dcavalca@meta.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nicolas@fjasle.eu \
--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