From: Philippe De Muyter <phdm@macqel.be>
To: Hidehiro Kawai <hidehiro.kawai.ez@hitachi.com>
Cc: Michael Kerrisk <mtk.manpages@googlemail.com>,
Michael Kerrisk <mtk.manpages@gmail.com>,
linux-kernel@vger.kernel.org,
libdc1394-devel@lists.sourceforge.net, stefanr@s5r6.in-berlin.de,
sugita <yumiko.sugita.yf@hitachi.com>,
Satoshi OSHIMA <satoshi.oshima.fk@hitachi.com>
Subject: Re: mmap'ed memory in core files ?
Date: Fri, 4 Jul 2008 13:13:18 +0200 [thread overview]
Message-ID: <20080704111318.GA28377@frolo.macqel> (raw)
In-Reply-To: <486DBA21.3080106@hitachi.com>
Hi Hidehiro,
On Fri, Jul 04, 2008 at 02:50:25PM +0900, Hidehiro Kawai wrote:
[...]
> > I see the following ways to solve my problem :
> > - do not tag the zone as VM_RESERVED in ieee1394::dma_region_mmap
> > - tag the zone as VM_ALWAYSDUMP in ieee1394::dma_region_mmap
> > - add a bit in coredump_filter to dump the VM_RESERVED zones.
> >
> > As I don't know the real meaning of VM_RESERVED, I do not know which choice
> > is the best one for the official kernel tree, but locally I'll go for
> > adding VM_ALWAYSDUMP in ieee1394::dma_region_mmap.
>
> I'm afraid I don't know real usages of VM_RESERVED and VM_IO, either.
> Allowing everyone to choose whether dump the dma region or not,
> perhaps we need to introduce a new VM flag (e.g. VM_DUMPABLE) and
> a coredump_filter bit which controls (VM_IO | VM_RESERVED) &&
> VM_DUMPABLE area, for example.
>
> I think it is also OK to just add VM_ALWAYSDUMP flag to the dma
> region if the device driver knows the region is safely readable
> and small enough.
I have just submitted a patch doing that for ieee1394 dma regions:
http://marc.info/?l=linux-kernel&m=121510404729225&w=2
Thanks for your help
Philippe
next prev parent reply other threads:[~2008-07-04 11:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 13:21 mmap'ed memory in core files ? Philippe De Muyter
2008-07-01 18:16 ` Michael Kerrisk
2008-07-01 21:44 ` Bron Gondwana
2008-07-02 5:14 ` Michael Kerrisk
2008-07-02 6:35 ` Rob Mueller
2008-07-02 11:07 ` Andi Kleen
2008-07-02 11:52 ` Bron Gondwana
2008-07-02 10:50 ` Philippe De Muyter
2008-07-02 10:58 ` Michael Kerrisk
2008-07-02 11:04 ` Philippe De Muyter
2008-07-02 12:24 ` Stefan Richter
2008-07-02 13:16 ` Philippe De Muyter
2008-07-03 3:51 ` Hidehiro Kawai
2008-07-03 9:22 ` Philippe De Muyter
2008-07-04 5:50 ` Hidehiro Kawai
2008-07-04 6:33 ` Stefan Richter
2008-07-04 11:25 ` Philippe De Muyter
2008-07-04 14:29 ` Hugh Dickins
2008-07-04 11:13 ` Philippe De Muyter [this message]
2008-07-03 9:37 ` Philippe De Muyter
2008-07-03 16:52 ` [PATCH] ieee1394 : dump mmapped video1394 buffers in core files Philippe De Muyter
2008-07-04 18:33 ` Stefan Richter
2008-07-04 20:49 ` Philippe De Muyter
2008-07-02 13:30 ` mmap'ed memory in core files ? Christoph Hellwig
2008-07-02 11:01 ` Philippe De Muyter
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=20080704111318.GA28377@frolo.macqel \
--to=phdm@macqel.be \
--cc=hidehiro.kawai.ez@hitachi.com \
--cc=libdc1394-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=mtk.manpages@googlemail.com \
--cc=satoshi.oshima.fk@hitachi.com \
--cc=stefanr@s5r6.in-berlin.de \
--cc=yumiko.sugita.yf@hitachi.com \
/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