Re: [patch 4/8] propagate error values from clone_mnt

Miklos Szeredi <[email protected]> writes:

> From: Miklos Szeredi <[email protected]>
>
> Allow clone_mnt() to return errors other than ENOMEM.  This will be
> used for returning a different error value when the number of user
> mounts goes over the limit.
>
> Fix copy_tree() to return EPERM for unbindable mounts.
>
> Don't propagate further from dup_mnt_ns() as that copy_tree() can only
> fail with -ENOMEM.

At a quick skim this looks ok.

Eric
-
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:
  • [patch 0/8] mount ownership and unprivileged mount syscall (v4)
    • From: Miklos Szeredi <[email protected]>
  • [patch 4/8] propagate error values from clone_mnt
    • From: Miklos Szeredi <[email protected]>

• Prev by Date: Re: [Announce] [patch] Modular Scheduler Core and Completely Fair Scheduler [CFS]
• Next by Date: Linux 2.6.20.7 - Hard Disk rumbling?
• Previous by thread: [patch 4/8] propagate error values from clone_mnt
• Next by thread: Re: [patch 0/8] mount ownership and unprivileged mount syscall (v4)
• 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]