Messages in this thread | | | Subject | Re: [PATCH -mm 1/9] unshare system call: system call handler function | From | (Eric W. Biederman) | Date | Fri, 16 Dec 2005 05:46:23 -0700 |
| |
Jamie Lokier <jamie@shareable.org> writes:
> Like clone(), unshare() will have to change from year to year, as new > flags are added. It would be good if the default behaviour of 0 bits > to unshare() also did the right thing, so that programs compiled in > 2006 still function as expected in 2010. Hmm, this > forward-compatibility does not look pretty.
Why all it requires is that whenever someone updates clone they update unshare. Given the tiniest bit of refactoring we should be able to share all of the interesting code paths.
Which should also improve maintenance considerably.
Eric - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |