Re: [openib-general] madvise MADV_DONTFORK/MADV_DOFORK

One question, which I'm too lazy to read the source to answer: what
does an old (pre-MADV_DONTFORK) kernel do with an application that
tries to set MADV_DONTFORK?

I'm wondering what portable applications will have to do to handle the
case of a new application running on an old kernel.

Thanks,
  Roland
-
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/

---

• References:
  • madvise MADV_DONTFORK/MADV_DOFORK
    • From: "Michael S. Tsirkin" <[email protected]>

• Prev by Date: Re: RFC: disk geometry via sysfs
• Next by Date: any FS with tree-based quota system?
• Previous by thread: Re: madvise MADV_DONTFORK/MADV_DOFORK
• Next by thread: 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]