Re: [PATCH] unshare: Cleanup up the sys_unshare interface before we are committed.

Eric W. Biederman writes:

> - We don't confuse users and developers about the inverted values of
>   the clone bits.

Given that the name starts with "un", I would *expect*
unshare(CLONE_FOO) to mean that I no longer want to share FOO.

If you want the argument to have the same sense as in the clone system
call, you will have to call it "share" rather than "unshare" (and then
explain to confused developers why they can't use it to start sharing
things that previously weren't shared :).

Paul.
-
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:
- Re: [PATCH] unshare: Cleanup up the sys_unshare interface before we are committed.
  - From: Linus Torvalds <[email protected]>
- Re: [PATCH] unshare: Cleanup up the sys_unshare interface before we are committed.
  - From: "Michael Kerrisk" <[email protected]>
- Re: [PATCH] unshare: Cleanup up the sys_unshare interface before we are committed.
  - From: Linus Torvalds <[email protected]>
- Re: [PATCH] unshare: Cleanup up the sys_unshare interface before we are committed.
  - From: [email protected] (Eric W. Biederman)

Prev by Date: Re: [PATCH] fix potential return of uninitialized variable in scsi_scan (resend)
Next by Date: Re: ext3_ordered_writepage() questions
Previous by thread: Re: [PATCH] unshare: Cleanup up the sys_unshare interface before we are committed.
Next by thread: [PATCH] i386: run BIOS PCI detection before direct
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]