Re: [PATCH v3 03/30] kho: warn if KHO is disabled due to an error

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Pasha Tatashin <pasha.tatashin@xxxxxxxxxx>
Subject: Re: [PATCH v3 03/30] kho: warn if KHO is disabled due to an error
From: Pratyush Yadav <pratyush@xxxxxxxxxx>
Date: Fri, 08 Aug 2025 13:48:04 +0200
Cc: pratyush@xxxxxxxxxx, jasonmiu@xxxxxxxxxx, graf@xxxxxxxxxx, changyuanl@xxxxxxxxxx, rppt@xxxxxxxxxx, dmatlack@xxxxxxxxxx, rientjes@xxxxxxxxxx, corbet@xxxxxxx, rdunlap@xxxxxxxxxxxxx, ilpo.jarvinen@xxxxxxxxxxxxxxx, kanie@xxxxxxxxxxxxxxxxx, ojeda@xxxxxxxxxx, aliceryhl@xxxxxxxxxx, masahiroy@xxxxxxxxxx, akpm@xxxxxxxxxxxxxxxxxxxx, tj@xxxxxxxxxx, yoann.congal@xxxxxxxx, mmaurer@xxxxxxxxxx, roman.gushchin@xxxxxxxxx, chenridong@xxxxxxxxxx, axboe@xxxxxxxxx, mark.rutland@xxxxxxx, jannh@xxxxxxxxxx, vincent.guittot@xxxxxxxxxx, hannes@xxxxxxxxxxx, dan.j.williams@xxxxxxxxx, david@xxxxxxxxxx, joel.granados@xxxxxxxxxx, rostedt@xxxxxxxxxxx, anna.schumaker@xxxxxxxxxx, song@xxxxxxxxxx, zhangguopeng@xxxxxxxxxx, linux@xxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, linux-doc@xxxxxxxxxxxxxxx, linux-mm@xxxxxxxxx, gregkh@xxxxxxxxxxxxxxxxxxx, tglx@xxxxxxxxxxxxx, mingo@xxxxxxxxxx, bp@xxxxxxxxx, dave.hansen@xxxxxxxxxxxxxxx, x86@xxxxxxxxxx, hpa@xxxxxxxxx, rafael@xxxxxxxxxx, dakr@xxxxxxxxxx, bartosz.golaszewski@xxxxxxxxxx, cw00.choi@xxxxxxxxxxx, myungjoo.ham@xxxxxxxxxxx, yesanishhere@xxxxxxxxx, Jonathan.Cameron@xxxxxxxxxx, quic_zijuhu@xxxxxxxxxxx, aleksander.lobakin@xxxxxxxxx, ira.weiny@xxxxxxxxx, andriy.shevchenko@xxxxxxxxxxxxxxx, leon@xxxxxxxxxx, lukas@xxxxxxxxx, bhelgaas@xxxxxxxxxx, wagi@xxxxxxxxxx, djeffery@xxxxxxxxxx, stuart.w.hayes@xxxxxxxxx, lennart@xxxxxxxxxxxxxx, brauner@xxxxxxxxxx, linux-api@xxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, saeedm@xxxxxxxxxx, ajayachandra@xxxxxxxxxx, jgg@xxxxxxxxxx, parav@xxxxxxxxxx, leonro@xxxxxxxxxx, witu@xxxxxxxxxx
In-reply-to: <20250807014442.3829950-4-pasha.tatashin@soleen.com>
User-agent: Gnus/5.13 (Gnus v5.13)

On Thu, Aug 07 2025, Pasha Tatashin wrote:

> During boot scratch area is allocated based on command line
> parameters or auto calculated. However, scratch area may fail
> to allocate, and in that case KHO is disabled. Currently,
> no warning is printed that KHO is disabled, which makes it
> confusing for the end user to figure out why KHO is not
> available. Add the missing warning message.
>
> Signed-off-by: Pasha Tatashin <pasha.tatashin@xxxxxxxxxx>
> Acked-by: Mike Rapoport (Microsoft) <rppt@xxxxxxxxxx>

Acked-by: Pratyush Yadav <pratyush@xxxxxxxxxx>

-- 
Regards,
Pratyush Yadav

References:
- [PATCH v3 00/30] Live Update Orchestrator
  - From: Pasha Tatashin
- [PATCH v3 03/30] kho: warn if KHO is disabled due to an error
  - From: Pasha Tatashin

Prev by Date: Re: [PATCH v3 02/30] kho: mm: Don't allow deferred struct page with KHO
Next by Date: Re: [PATCH v19 00/27] riscv control-flow integrity for usermode
Previous by thread: [PATCH v3 03/30] kho: warn if KHO is disabled due to an error
Next by thread: [PATCH v3 04/30] kho: allow to drive kho from within kernel
Index(es):
- Date
- Thread

[Index of Archives] [Linux Ext4 Filesystem] [Union Filesystem] [Filesystem Testing] [Ceph Users] [Ecryptfs] [NTFS 3] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [NTFS 3] [Samba] [Device Mapper] [CEPH Development]