From: Andreas Schwab <schwab@linux-m68k.org>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: vmlinux ELF header sometimes corrupt
Date: Fri, 24 Jan 2020 14:14:05 +0100 [thread overview]
Message-ID: <87sgk5m1ya.fsf@igel.home> (raw)
In-Reply-To: <71aa76d0-a3b8-b4f3-a7c3-766cfb75412f@rasmusvillemoes.dk> (Rasmus Villemoes's message of "Wed, 22 Jan 2020 18:52:21 +0100")
On Jan 22 2020, Rasmus Villemoes wrote:
> So the inode number and mtime/ctime are exactly the same, but for some
> reason Blocks: has changed? This is on an ext4 filesystem, but I don't
> suspect the filesystem to be broken, because it's always just vmlinux
> that ends up corrupt, and always in exactly this way with the first 52
> bytes having been wiped.
Note that the size of the ELF header (Elf32_Ehdr) is 52 bytes.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
WARNING: multiple messages have this Message-ID (diff)
From: Andreas Schwab <schwab@linux-m68k.org>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Subject: Re: vmlinux ELF header sometimes corrupt
Date: Fri, 24 Jan 2020 14:14:05 +0100 [thread overview]
Message-ID: <87sgk5m1ya.fsf@igel.home> (raw)
In-Reply-To: <71aa76d0-a3b8-b4f3-a7c3-766cfb75412f@rasmusvillemoes.dk> (Rasmus Villemoes's message of "Wed, 22 Jan 2020 18:52:21 +0100")
On Jan 22 2020, Rasmus Villemoes wrote:
> So the inode number and mtime/ctime are exactly the same, but for some
> reason Blocks: has changed? This is on an ext4 filesystem, but I don't
> suspect the filesystem to be broken, because it's always just vmlinux
> that ends up corrupt, and always in exactly this way with the first 52
> bytes having been wiped.
Note that the size of the ELF header (Elf32_Ehdr) is 52 bytes.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
WARNING: multiple messages have this Message-ID (diff)
From: Andreas Schwab <schwab@linux-m68k.org>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
"linuxppc-dev\@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: vmlinux ELF header sometimes corrupt
Date: Fri, 24 Jan 2020 14:14:05 +0100 [thread overview]
Message-ID: <87sgk5m1ya.fsf@igel.home> (raw)
In-Reply-To: <71aa76d0-a3b8-b4f3-a7c3-766cfb75412f@rasmusvillemoes.dk> (Rasmus Villemoes's message of "Wed, 22 Jan 2020 18:52:21 +0100")
On Jan 22 2020, Rasmus Villemoes wrote:
> So the inode number and mtime/ctime are exactly the same, but for some
> reason Blocks: has changed? This is on an ext4 filesystem, but I don't
> suspect the filesystem to be broken, because it's always just vmlinux
> that ends up corrupt, and always in exactly this way with the first 52
> bytes having been wiped.
Note that the size of the ELF header (Elf32_Ehdr) is 52 bytes.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2020-01-24 13:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 17:52 vmlinux ELF header sometimes corrupt Rasmus Villemoes
2020-01-22 17:52 ` Rasmus Villemoes
2020-01-24 10:50 ` Michael Ellerman
2020-01-24 10:50 ` Michael Ellerman
2020-01-24 10:50 ` Michael Ellerman
2020-01-24 11:16 ` Rasmus Villemoes
2020-01-24 11:16 ` Rasmus Villemoes
2020-01-24 13:14 ` Andreas Schwab [this message]
2020-01-24 13:14 ` Andreas Schwab
2020-01-24 13:14 ` Andreas Schwab
2020-01-28 8:12 ` Rasmus Villemoes
2020-01-28 8:12 ` Rasmus Villemoes
2020-02-27 15:57 ` Rasmus Villemoes
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=87sgk5m1ya.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=linuxppc-dev@lists.ozlabs.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 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.