public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Wu <lekensteyn@gmail.com>
To: Al Viro <viro@zeniv.linux.org.uk>, linux-kernel@vger.kernel.org
Subject: [REGRESSION] coredumps truncated after "new helper: dump_align()"
Date: Fri, 15 Nov 2013 15:26:10 +0100	[thread overview]
Message-ID: <11835033.kIc1RH0rS1@al> (raw)

Hi Al,

Somewhere in the merge window of 3.13, coredumps appear truncated.
Instead of 319488 bytes, I get 868 bytes (tested with x86_64 only).

The latest Linus' master (v3.12-9579-g049ffa8) is still affected.
Bisection leads to:

commit 22a8cb8248ba5d340307ba72432253b1dbdb5cf7
Author: Al Viro <viro@zeniv.linux.org.uk>
Date:   Tue Oct 8 11:05:01 2013 -0400

    new helper: dump_align()
    
    dump_skip to given alignment...
    
    Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>

:040000 040000 880920de653955485453c8cc11045bb09e2934f7 f8b348d32b59ae7a16cbc3eb2a6319f4df0210eb M      arch
:040000 040000 eaeffe2378806e95d23b3f3a9dc0fa8f078d6052 88866abde93296a05b4adda869280bc05403936f M      fs
:040000 040000 218263e01dd7473998c54a5a68ed5ae072854d24 ff531dce919862b662fef19a9a049f0de3db38ce M      include

I first noticed this bug on my laptop (v3.12-7033-g42a2d92) and
reproduced this bug in a QEMU virtual machine too. If you want, I
can also provide the git bisect script that starts QEMU and tests
the serial output. That allows a kernel to be verified in two seconds
(minus build times).

Regards,
Peter

             reply	other threads:[~2013-11-15 14:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-15 14:26 Peter Wu [this message]
2013-11-15 20:38 ` [REGRESSION] coredumps truncated after "new helper: dump_align()" Al Viro
2013-11-15 20:57   ` Joe Perches
2013-11-15 21:34   ` Peter Wu
2013-11-16  0:04     ` Al Viro
2013-11-17  6:19       ` Al Viro
2013-11-17  9:59         ` Peter Wu

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=11835033.kIc1RH0rS1@al \
    --to=lekensteyn@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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