[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5501D8CF.7020204@redhat.com>
Date: Thu, 12 Mar 2015 18:19:59 +0000
From: Pedro Alves <palves@...hat.com>
To: Oleg Nesterov <oleg@...hat.com>,
Andy Lutomirski <luto@...capital.net>
CC: Jan Kratochvil <jan.kratochvil@...hat.com>,
Sergio Durigan Junior <sergiodj@...hat.com>,
GDB Patches <gdb-patches@...rceware.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: vvar, gup && coredump
On 03/12/2015 05:46 PM, Oleg Nesterov wrote:
> On 03/12, Oleg Nesterov wrote:
>>
>> Yes, this is true. OK, lets not dump it.
>
> OTOH. We can probably add ->access() into special_mapping_vmops, this
> way __access_remote_vm() could work even if gup() fails ?
>
> Jan, Sergio. How much do we want do dump this area ? The change above
> should be justified.
Memory mappings that weren't touched since they were initially mapped can
be retrieved from the program binary and the shared libraries, even if
the core dump is moved to another machine. However, in vvar case,
sounds like there's nowhere to read it from offline? In that case,
it could be justified to dump it.
Thanks,
Pedro Alves
--
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/
Powered by blists - more mailing lists