From: Will Deacon <will@kernel.org>
To: Pavel Tatashin <pasha.tatashin@soleen.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, jmorris@namei.org,
catalin.marinas@arm.com, tyhicks@linux.microsoft.com
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>
Subject: Re: [PATCH] arm64: kdump: update ppos when reading elfcorehdr
Date: Mon, 22 Mar 2021 13:19:57 +0000 [thread overview]
Message-ID: <161641719902.3900979.10337880549161097433.b4-ty@kernel.org> (raw)
In-Reply-To: <20210319205054.743368-1-pasha.tatashin@soleen.com>
On Fri, 19 Mar 2021 16:50:54 -0400, Pavel Tatashin wrote:
> The ppos points to a position in the old kernel memory (and in case of
> arm64 in the crash kernel since elfcorehdr is passed as a segment). The
> function should update the ppos by the amount that was read. This bug is
> not exposed by accident, but other platforms update this value properly.
> So, fix it in ARM64 version of elfcorehdr_read() as well.
Applied to arm64 (for-next/fixes), thanks!
[1/1] arm64: kdump: update ppos when reading elfcorehdr
https://git.kernel.org/arm64/c/141f8202cfa4
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: Pavel Tatashin <pasha.tatashin@soleen.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, jmorris@namei.org,
catalin.marinas@arm.com, tyhicks@linux.microsoft.com
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>
Subject: Re: [PATCH] arm64: kdump: update ppos when reading elfcorehdr
Date: Mon, 22 Mar 2021 13:19:57 +0000 [thread overview]
Message-ID: <161641719902.3900979.10337880549161097433.b4-ty@kernel.org> (raw)
In-Reply-To: <20210319205054.743368-1-pasha.tatashin@soleen.com>
On Fri, 19 Mar 2021 16:50:54 -0400, Pavel Tatashin wrote:
> The ppos points to a position in the old kernel memory (and in case of
> arm64 in the crash kernel since elfcorehdr is passed as a segment). The
> function should update the ppos by the amount that was read. This bug is
> not exposed by accident, but other platforms update this value properly.
> So, fix it in ARM64 version of elfcorehdr_read() as well.
Applied to arm64 (for-next/fixes), thanks!
[1/1] arm64: kdump: update ppos when reading elfcorehdr
https://git.kernel.org/arm64/c/141f8202cfa4
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-03-22 13:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 20:50 [PATCH] arm64: kdump: update ppos when reading elfcorehdr Pavel Tatashin
2021-03-19 20:50 ` Pavel Tatashin
2021-03-19 21:07 ` Tyler Hicks
2021-03-19 21:07 ` Tyler Hicks
2021-03-22 13:19 ` Will Deacon [this message]
2021-03-22 13:19 ` Will Deacon
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=161641719902.3900979.10337880549161097433.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=jmorris@namei.org \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pasha.tatashin@soleen.com \
--cc=tyhicks@linux.microsoft.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.