On Tue, Dec 4, 2012 at 6:10 AM, Stanislav Kinsbursky <skinsbur...@parallels.com> wrote:
> But there should be noted, that such implementation introduces limitation > (Trond's quote): > "That approach can fall afoul of the selinux restrictions on the process > context. Processes that are allowed to write data, may not be allowed to > create sockets or call connect(). That is the main reason for doing it > in the rpciod context, which is a clean kernel process context." So you tested this and Trond was wrong? This work just fine even on an SELinux box? Or it does break tons and tons of people's computers? -Eric -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
