From: Pratyush Yadav <pratyush@kernel.org>
To: Mike Rapoport <rppt@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Alexander Graf <graf@amazon.com>, Baoquan He <bhe@redhat.com>,
Changyuan Lyu <changyuanl@google.com>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Pratyush Yadav <pratyush@kernel.org>,
Shuah Khan <shuah@kernel.org>,
Thomas Weischuh <linux@weissschuh.net>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 2/3] lib/test_kho: fixes for error handling
Date: Wed, 13 Aug 2025 15:50:24 +0200 [thread overview]
Message-ID: <mafs0y0rnuy8v.fsf@kernel.org> (raw)
In-Reply-To: <20250811082510.4154080-3-rppt@kernel.org>
On Mon, Aug 11 2025, Mike Rapoport wrote:
> From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
>
> * Update kho_test_save() so that folios array won't be freed when
> returning from the function and the fdt will be freed on error
> * Reset state->nr_folios to 0 in kho_test_generate_data() on error
> * Simplify allocation of folios info in fdt.
>
> Reported-by: Pratyush Yadav <pratyush@kernel.org>
> Closes: https://lore.kernel.org/all/mafs0zfcjcepf.fsf@kernel.org
> Fixes: b753522bed0b ("kho: add test for kexec handover")
> Signed-off-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
Reviewed-by: Pratyush Yadav <pratyush@kernel.org>
--
Regards,
Pratyush Yadav
next prev parent reply other threads:[~2025-08-13 13:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 8:25 [PATCH 0/3] kho: fixes and cleanups Mike Rapoport
2025-08-11 8:25 ` [PATCH 1/3] kho: allow scratch areas with zero size Mike Rapoport
2025-08-13 13:45 ` Pratyush Yadav
2025-08-13 14:07 ` Mike Rapoport
2025-08-13 14:25 ` Pratyush Yadav
2025-08-11 8:25 ` [PATCH 2/3] lib/test_kho: fixes for error handling Mike Rapoport
2025-08-13 13:50 ` Pratyush Yadav [this message]
2025-08-11 8:25 ` [PATCH 3/3] selftest/kho: update generation of initrd Mike Rapoport
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=mafs0y0rnuy8v.fsf@kernel.org \
--to=pratyush@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=changyuanl@google.com \
--cc=graf@amazon.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@weissschuh.net \
--cc=pasha.tatashin@soleen.com \
--cc=rppt@kernel.org \
--cc=shuah@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