From: Al Viro <viro@ZenIV.linux.org.uk>
To: Peter Wu <lekensteyn@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [REGRESSION] coredumps truncated after "new helper: dump_align()"
Date: Sun, 17 Nov 2013 06:19:07 +0000 [thread overview]
Message-ID: <20131117061907.GL13318@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20131116000408.GK13318@ZenIV.linux.org.uk>
On Sat, Nov 16, 2013 at 12:04:08AM +0000, Al Viro wrote:
> On Fri, Nov 15, 2013 at 10:34:43PM +0100, Peter Wu wrote:
>
> > Unfortunately, this patch still does not fix the issue. I rm'd the output
> > directory just to be sure, but the bug is still there. What does this commit
> > do anyway? The commit message is quite vague.
>
> Introduces a helper that used to be open-coded in a bunch of places -
> pads the coredump to given alignment. And switches those places
> to that new helper...
>
> FWIW, I haven't tried that on your config yet, but here (with the patch
> in my previous mail) I'm seeing a sane-looking coredump -
> -rw------- 1 root root 315392 Nov 15 17:48 core
> Different userland, presumably, since that static binary is 684349
> bytes long.
>
> I'll try to reproduce with your config...
... and on your config I'm seeing
Inited
Segmentation fault (core dumped)
[ 0.123351] Core size: 315392
in the log. Same size, same apparently sane coredump. Can you check what you
get on mainline + diff below (combination of dump_align() and locking fix)?
diff --git a/fs/coredump.c b/fs/coredump.c
index 62406b6..bc3fbcd 100644
--- a/fs/coredump.c
+++ b/fs/coredump.c
@@ -695,7 +695,7 @@ int dump_emit(struct coredump_params *cprm, const void *addr, int nr)
while (nr) {
if (dump_interrupted())
return 0;
- n = vfs_write(file, addr, nr, &pos);
+ n = __kernel_write(file, addr, nr, &pos);
if (n <= 0)
return 0;
file->f_pos = pos;
@@ -733,7 +733,7 @@ int dump_align(struct coredump_params *cprm, int align)
{
unsigned mod = cprm->written & (align - 1);
if (align & (align - 1))
- return -EINVAL;
- return mod ? dump_skip(cprm, align - mod) : 0;
+ return 0;
+ return mod ? dump_skip(cprm, align - mod) : 1;
}
EXPORT_SYMBOL(dump_align);
next prev parent reply other threads:[~2013-11-17 6:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 14:26 [REGRESSION] coredumps truncated after "new helper: dump_align()" Peter Wu
2013-11-15 20:38 ` 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 [this message]
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=20131117061907.GL13318@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=lekensteyn@gmail.com \
--cc=linux-kernel@vger.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 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.