Re: [PATCH] namespace: ensure clone_flags are always stored in an unsigned long

Eric W. Biederman wrote:
> While working on unshare support for the network namespace I noticed
> we were putting clone flags in an int.  Which is weird because the
> syscall uses unsigned long and we at least need an unsigned to
> properly hold all of the unshare flags. 
> 
> So to make the code consistent, this patch updates the code to use
> unsigned long instead of int for the clone flags in those places
> where we get it wrong today.
> 
> Signed-off-by: Eric W. Biederman <[email protected]>

we definitely want to do that. I have a similar patch waiting for 
next -mm doing the same.

Acked-by : Cedric Le Goater <[email protected]>

C.
-
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] namespace: ensure clone_flags are always stored in an unsigned long
    • From: [email protected] (Eric W. Biederman)

• Prev by Date: Re: [PATCH -rt] irq nobody cared workaround for i386
• Next by Date: Re: [patch] CFS scheduler, -v17
• Previous by thread: [PATCH] namespace: ensure clone_flags are always stored in an unsigned long
• Next by thread: [PATCH -rt] CONFIG_PARAVIRT and CONFIG_MCOUNT don't play well together
• 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]