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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 4 Jul 2008 13:13:18 +0200
From:	Philippe De Muyter <>
To:	Hidehiro Kawai <>
Cc:	Michael Kerrisk <>,
	Michael Kerrisk <>,,,,
	sugita <>,
	Satoshi OSHIMA <>
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:

Thanks for your help

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists