netdev - Re: [PATCH 1/12] L2 network namespace (v3): current network namespace operations

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <m1hcup8l4t.fsf@ebiederm.dsl.xmission.com>
Date:	Wed, 17 Jan 2007 13:16:02 -0700
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Dmitry Mishin <dim@...nvz.org>
Cc:	containers@...ts.osdl.org, alexey@...ru, netdev@...r.kernel.org,
	saw@...ru
Subject: Re: [PATCH 1/12] L2 network namespace (v3): current network namespace operations

Dmitry Mishin <dim@...nvz.org> writes:

> Added functions and macros required to operate with network namespaces.
> They are required in order to switch network namespace for incoming packets and
> to not extend current network interface by additional network namespace argue.

Is exec_net only used in interrupt context?
Or how do you ensure a sleeping function does not get called and the
kernel process comes back on another cpu?

Eric
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html