>> I was, however, the flaws that you complained of had nothing to
>> do with the syscall -- it's all in the syscall wrapper (which is
>> required for clone(), like it or not.)
The issue is not whether a wrapper is needed or not.
My point is that it is cleaner to always describe stack areas as
memory areas (e.g., as a base/size pair). Note that this is
effectively what's happening in the platform-independent part of the
kernel today.
--david
-
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/