[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080704111318.GA28377@frolo.macqel>
Date: Fri, 4 Jul 2008 13:13:18 +0200
From: Philippe De Muyter <phdm@...qel.be>
To: Hidehiro Kawai <hidehiro.kawai.ez@...achi.com>
Cc: Michael Kerrisk <mtk.manpages@...glemail.com>,
Michael Kerrisk <mtk.manpages@...il.com>,
linux-kernel@...r.kernel.org,
libdc1394-devel@...ts.sourceforge.net, stefanr@...6.in-berlin.de,
sugita <yumiko.sugita.yf@...achi.com>,
Satoshi OSHIMA <satoshi.oshima.fk@...achi.com>
Subject: Re: mmap'ed memory in core files ?
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
--
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