Re: [openib-general] Re: madvise MADV_DONTFORK/MADV_DOFORK

On Mon, 13 Feb 2006, Michael S. Tsirkin wrote:
> 
> Like this then?

Almost.  I would still prefer madvise_vma to allow MADV_DONTFORK
on a VM_IO vma, even though it must prohibit MADV_DOFORK there.
But if Linus disagrees, of course ignore me.

Comments much better, thanks.  I didn't get your point about mlock'd
memory, but I'm content to believe you're thinking of an issue that
hasn't occurred to me.

Hugh
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: [openib-general] Re: madvise MADV_DONTFORK/MADV_DOFORK
  - From: Linus Torvalds <[email protected]>
- Re: [openib-general] Re: madvise MADV_DONTFORK/MADV_DOFORK
  - From: "Michael S. Tsirkin" <[email protected]>

References:
- madvise MADV_DONTFORK/MADV_DOFORK
  - From: "Michael S. Tsirkin" <[email protected]>
- Re: madvise MADV_DONTFORK/MADV_DOFORK
  - From: Linus Torvalds <[email protected]>
- Re: [openib-general] Re: madvise MADV_DONTFORK/MADV_DOFORK
  - From: Roland Dreier <[email protected]>
- Re: [openib-general] Re: madvise MADV_DONTFORK/MADV_DOFORK
  - From: Linus Torvalds <[email protected]>
- Re: [openib-general] Re: madvise MADV_DONTFORK/MADV_DOFORK
  - From: Hugh Dickins <[email protected]>
- Re: [openib-general] Re: madvise MADV_DONTFORK/MADV_DOFORK
  - From: "Michael S. Tsirkin" <[email protected]>

Prev by Date: Re: Random reboots
Next by Date: Re: [PATCH 02/13] hrtimer: remove useless const
Previous by thread: Re: [openib-general] Re: madvise MADV_DONTFORK/MADV_DOFORK
Next by thread: Re: [openib-general] Re: madvise MADV_DONTFORK/MADV_DOFORK
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]