Cedric Le Goater wrote:
Ilpo Järvinen wrote:
On Wed, 5 Dec 2007, Andrew Morton wrote:
On Thu, 06 Dec 2007 17:59:37 +1100 Reuben Farrelly [EMAIL PROTECTED]
wrote:
This non fatal oops which I have just noticed may be related to this
change then
- certainly looks networking related.
yep
Andrew Morton wrote:
Temporarily at
http://userweb.kernel.org/~akpm/2.6.24-rc4-mm1/
Will appear later at
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.24-rc4/2.6.24-rc4-mm1/
I got this one while compiling on NFS.
C.
kernel BUG at
Ilpo Järvinen wrote:
On Thu, 13 Dec 2007, Cedric Le Goater wrote:
I got this one while compiling on NFS.
C.
kernel BUG at /home/legoater/linux/2.6.24-rc4-mm1/include/net/tcp.h:1480!
I'm not exactly sure what patches you have applied and which patches are
not, with rc4-mm1
Ilpo Järvinen wrote:
On Wed, 5 Dec 2007, David Miller wrote:
From: Reuben Farrelly [EMAIL PROTECTED]
Date: Thu, 06 Dec 2007 17:59:37 +1100
On 5/12/2007 4:17 PM, Andrew Morton wrote:
- Lots of device IDs have been removed from the e1000 driver and moved over
to e1000e. So if your e1000
Ilpo Järvinen wrote:
On Wed, 5 Dec 2007, Andrew Morton wrote:
On Thu, 06 Dec 2007 17:59:37 +1100 Reuben Farrelly [EMAIL PROTECTED] wrote:
This non fatal oops which I have just noticed may be related to this change
then
- certainly looks networking related.
yep, but it isn't e1000. It's
that helped going a little further in the boot process but we then have
a network issue when bringing the network interface up :
please cc netdev on network issues.
yes.
Bringing up interface eth0: Ý cut here ¨
Kernel BUG at 0002 Ýverbose debug info
Martin Schwidefsky wrote:
On Fri, 2007-10-19 at 11:16 +0200, Cedric Le Goater wrote:
This is the vmlinux.lds.S problem. The cleanup patch from Sam Ravnborg
moved the __initramfs_start and __initramfs_end symbols into
the .init.ramfs section. This is in itself not a problem, but it
surfaced
Ilpo Järvinen wrote:
On Wed, 3 Oct 2007, Cedric Le Goater wrote:
Cedric Le Goater wrote:
Below are the messages I got on 2) right after running ketchup (which does
a wget www.kernel.org)
Oops, those tcp_fragment WARNINGs in the other mail were due to bug in
the debug patch
Hello Ilpo !
Ilpo Järvinen wrote:
Hi Dave,
Sacktag fastpath_cnt_hint seems to be very tricky to get right...
I suppose this one fixes Cedric's case. I cannot say for sure
until there is something more definite indication of
tcp_retrans_try_collapse origin than what the simple late
Ilpo Järvinen wrote:
On Wed, 3 Oct 2007, Cedric Le Goater wrote:
Ilpo Järvinen wrote:
Sacktag fastpath_cnt_hint seems to be very tricky to get right...
I suppose this one fixes Cedric's case. I cannot say for sure
until there is something more definite indication
Ilpo Järvinen wrote:
On Wed, 3 Oct 2007, Cedric Le Goater wrote:
Ilpo Järvinen wrote:
On Wed, 3 Oct 2007, Cedric Le Goater wrote:
I'm dropping the previous patches you sent me and switching to this
patchset.
right ?
Yes you can do that... However, there are two ways forward:
1) Drop
Ilpo Järvinen wrote:
On Wed, 3 Oct 2007, Cedric Le Goater wrote:
Ilpo Järvinen wrote:
Ah, that's path 1) then... Since you seem to have enough time, I would say
that the path 1 is good as well and bugs unrelated to the fix will show up
there too...
arg. yes. sorry for the confusion.
I
Cedric Le Goater wrote:
Ilpo Järvinen wrote:
On Wed, 3 Oct 2007, Cedric Le Goater wrote:
Ilpo Järvinen wrote:
Ah, that's path 1) then... Since you seem to have enough time, I would say
that the path 1 is good as well and bugs unrelated to the fix will show up
there too...
arg. yes. sorry
Cedric Le Goater wrote:
Ilpo Järvinen wrote:
On Wed, 3 Oct 2007, Cedric Le Goater wrote:
Ilpo Järvinen wrote:
Ah, that's path 1) then... Since you seem to have enough time, I would say
that the path 1 is good as well and bugs unrelated to the fix will show up
there too...
arg. yes. sorry
Ilpo Järvinen wrote:
On Sat, 29 Sep 2007, Cedric Le Goater wrote:
Ilpo Järvinen wrote:
On Fri, 28 Sep 2007, Ilpo Järvinen wrote:
On Fri, 28 Sep 2007, Cedric Le Goater wrote:
I just found that warning in my logs. It seems that it's been
happening since rc7-mm1 at least.
WARNING
Ilpo Järvinen wrote:
On Fri, 28 Sep 2007, Ilpo Järvinen wrote:
On Fri, 28 Sep 2007, Cedric Le Goater wrote:
I just found that warning in my logs. It seems that it's been
happening since rc7-mm1 at least.
WARNING: at /home/legoater/linux/2.6.23-rc8-mm2/net/ipv4/tcp_input.c:2314
Hello !
Andrew Morton wrote:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc8/2.6.23-rc8-mm2/
I just found that warning in my logs. It seems that it's been
happening since rc7-mm1 at least.
Thanks !
C.
WARNING: at
Andrew Morton wrote:
On Fri, 28 Sep 2007 11:12:13 +0200 Cedric Le Goater [EMAIL PROTECTED] wrote:
Cedric made a good point that we will have conflicts of code
being added to the same place in nsproxy.c and the like. So
I copied Andrew to give him a heads up.
here's a suggestion,
we could
Eric W. Biederman wrote:
David Miller [EMAIL PROTECTED] writes:
Eric, pick an appropriate new non-conflicting number NOW.
Done. My apologies for the confusion. I thought the
way Cedric and the IBM guys were testing someone would have
shouted at me long before now.
This adds
Eric W. Biederman wrote:
This patch allows you to create a new network namespace
using sys_clone, or sys_unshare.
As the network namespace is still experimental and under development
clone and unshare support is only made available when CONFIG_NET_NS is
selected at compile time.
As this
Dmitry Mishin wrote:
This is an update of L2 network namespaces patches. They are applicable
to Cedric's 2.6.20-rc4-mm1-lxc2 tree.
Changes:
- updated to 2.6.20-rc4-mm1-lxc2
- current network context is per-CPU now
- fixed compilation without CONFIG_NET_NS
Changed
Eric W. Biederman wrote:
This family of containers are used too for HPC (high performance computing)
and
for distributed checkpoint/restart. The cluster runs hundred of jobs,
spawning
them on different hosts inside an application container. Usually the jobs
communicates with broadcast and
Kir Kolyshkin wrote:
snip
I am not sure about network isolation (used by Linux-VServer), but as
it comes for level2 vs. level3 virtualization, I see a need for both.
Here is the easy-to-understand comparison which can shed some light:
Serge E. Hallyn wrote:
The last one in your diagram confuses me - why foo0:1? I would
have thought it'd be
just thinking aloud. I thought that any kind/type of interface could be
mapped from host to guest.
host | guest 0 | guest 1 | guest2
Eric W. Biederman wrote:
Despite what it might look like unix domain sockets do not live in the
filesystem. They store a cookie in the filesystem that roughly
corresponds to the port number of an AF_INET socket. When you open a
socket the lookup is done by the cookie retrieved from the
Hello,
Eric W. Biederman wrote:
Thinking about this I am going to suggest a slightly different direction
for get a patchset we can merge.
First we concentrate on the fundamentals.
- How we mark a device as belonging to a specific network namespace.
- How we mark a socket as belonging to a
26 matches
Mail list logo
