From: Omar Sandoval <osandov@osandov.com>
To: Alexander Gordeev <agordeev@linux.ibm.com>
Cc: "Petr Tesařík" <petr@tesarici.cz>,
linux-s390@vger.kernel.org,
"Ilya Leoshkevich" <iii@linux.ibm.com>,
linux-debuggers@vger.kernel.org
Subject: Re: Incorrect vmcoreinfo KERNELOFFSET after "s390/boot: Rework deployment of the kernel image"
Date: Tue, 27 Aug 2024 12:38:28 -0700 [thread overview]
Message-ID: <Zs4rNF9x3NUl2AkT@telecaster.dhcp.thefacebook.com> (raw)
In-Reply-To: <Zsw7RU6gYHFkw9YI@li-008a6a4c-3549-11b2-a85c-c5cc2836eea2.ibm.com>
On Mon, Aug 26, 2024 at 10:22:29AM +0200, Alexander Gordeev wrote:
> > On Fri, Jul 12, 2024 at 07:17:38AM -0700, Omar Sandoval wrote:
> Hi Omar,
> ..
> > We have different approaches in how to get it done, which are
> > being investigated.
>
> Could you please check whether the recent kernel solves the issue.
>
> Thanks!
Yes, this appears to be fixed in 6.11-rc5. Thank you!
(Now that this issue is fixed, I can see that drgn has some legitimate
test failures on s390x caused by the paddr/vaddr split, but that needs
to be fixed in drgn.)
Thanks,
Omar
prev parent reply other threads:[~2024-08-27 19:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 23:34 Incorrect vmcoreinfo KERNELOFFSET after "s390/boot: Rework deployment of the kernel image" Omar Sandoval
2024-06-24 13:29 ` Alexander Gordeev
2024-06-27 13:51 ` Alexander Gordeev
2024-07-09 19:21 ` Petr Tesařík
2024-07-09 20:55 ` Omar Sandoval
2024-07-10 5:02 ` Petr Tesařík
2024-07-10 8:56 ` Alexander Gordeev
2024-07-11 23:55 ` Omar Sandoval
2024-07-10 8:53 ` Alexander Gordeev
2024-07-11 23:30 ` Omar Sandoval
2024-07-12 13:42 ` Alexander Gordeev
2024-07-12 14:17 ` Omar Sandoval
2024-07-15 10:06 ` Alexander Gordeev
2024-08-26 8:22 ` Alexander Gordeev
2024-08-27 19:38 ` Omar Sandoval [this message]
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=Zs4rNF9x3NUl2AkT@telecaster.dhcp.thefacebook.com \
--to=osandov@osandov.com \
--cc=agordeev@linux.ibm.com \
--cc=iii@linux.ibm.com \
--cc=linux-debuggers@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=petr@tesarici.cz \
/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