My netns patches updated to Linus' latest

Eric W. Biederman ebiederm at
Thu Jul 19 06:53:16 PDT 2007

"Denis V. Lunev" <den at> writes:

> Eric W. Biederman wrote:
>> My next project is most likely going to be to dig in and make the
>> loopback device a normal network device (not statically allocated)
>> as a cleanup in preparation for the network namespace work.
> I can do this :)
> As far as I understand the code, loopback device is used in two fashions:
> - as a real network device
> - and as a "stable" never freed piece of memory
> I presume, they should be separated.

Essentially.  As far as that goes I think my patchset already covers that
aspect of it.  Although there may be an initialization or shutdown
races that I currently do not handle.

Right now I'm working on a building up a clean patchset, and one of
the basic rules is that cleanups should happen before features are
added.  Which means that before we move a pointer to the loopback
device into a per network namespace structure we should make it
dynamically allocated if possible.

> As for device itself, there is a some sort of a template in a Pavel's
> virtual ethernet device driver...

Yes.  The tricky bits are mostly in the code review for making
certain that the loopback device isn't used after it is freed.

>> Feel free to pick the patches apart.   Especially in the core of the
>> network stack.
> I think that a small plan of submitting process is a good idea, at least
> we will be able to coordinate the efforts and work in parallel.

Yes.  Working in parallel would be good.  However the bottleneck I
see is is patch submission, review and acceptance.  Not so much
development of working patches.

So as much internal review and testing we can do before the patches
get to Dave Miller the better our chances (so long as we continue to
think about what is best for the network stack as a whole and not what
is best for network namespaces).


More information about the Containers mailing list