linux-kernel - Re: [PATCH 1/1] x86: Add process memory layout to coredump file

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAE04G=BvDFrAu2SoY5sQ9XjoFh9g2kp-gbzO0ETC2i4XMqi0AQ@mail.gmail.com>
Date:	Sun, 18 Dec 2011 20:37:55 +0800
From:	t cheney <cdmalord@...il.com>
To:	Al Viro <viro@...iv.linux.org.uk>
Cc:	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	gdb-patches@...rceware.org, binutils@...rceware.org
Subject: Re: [PATCH 1/1] x86: Add process memory layout to coredump file

On 12/15/11, Al Viro <viro@...iv.linux.org.uk> wrote:
> On Sat, Dec 10, 2011 at 10:37:02PM +0800, t cheney wrote:
>> This patch just add memory layout(same as /proc/pid/maps) to
>> coredump file. The layout is appended to corenote segment with
>> flag NT_MAPS=7.
>
>> +		len = sprintf(buf, "%08lx-%08lx %c%c%c%c %08llx %02x:%02x %lu",
>> +			start,
>> +			end,
>> +			flags & VM_READ ? 'r' : '-',
>> +			flags & VM_WRITE ? 'w' : '-',
>> +			flags & VM_EXEC ? 'x' : '-',
>> +			flags & VM_MAYSHARE ? 's' : 'p',
>> +			pgoff,
>> +			MAJOR(dev), MINOR(dev), ino);
>
> Device numbers may be wider than 16 bits.
Yes, it should be:
len = sprintf(buf, "%08lx-%08lx %c%c%c%c %08llx %03x:%05x %lu",
and  corresponding change from 25 to 29 in function pad_spaces:
static int pad_spaces(char *p, int len)
{
       len = 29 + sizeof(void *) * 6 - len;

>
>> +			p = d_path(&vma->vm_file->f_path, s, maps_size-1);
>
> What if somebody renames the file (or, better yet, its parent directory)
> between two calls of that thing?
>
Yes, function core_handle_maps is called twice, first one just calculate size,
second one write maps into coredump file. If the pathname is changed,
the size may changed too.
If the new size is less than or same as origin, all maps string is
written to file.
If the new size is  more than  origin, just part is written to file,
the rest is ignored.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/