Recently the documentation in Documentation/nfsroot.txt was
update to note that in fact ip=off and ip=::off as the
latter is ignored and the default (on) is used.
This was certainly a step in the direction of reducing confusion.
But it seems to me that the code ought to be fixed up so that
Hi Jeff,
ACK, pass this through paulus?
Yes, that's fine for me.
Thanks,
Jochen
--
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Mon, Dec 17, 2007 at 08:18:38PM -0500, Jeff Garzik wrote:
Changes to last version:
- Use inline functions for dma_sync_* instead of macros (suggested by Ralf)
- added Kconfig change to make selection for similair SGI boxes easier
hrm, could you rediff? it doesn't seem to apply
sure,
Hello,
the problem seems to be gone in 2.6.24-rc kernels.
--
Lukáš Hejtmánek
--
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi David.
On Tue, Dec 18, 2007 at 12:00:04PM +1100, David Chinner ([EMAIL PROTECTED])
wrote:
On Mon, Dec 17, 2007 at 06:03:38PM +0300, Evgeniy Polyakov wrote:
DST passed all FS tests in LTP with XFS (modulo MAX_LOCK_DEPTH too low bug:
[ 8398.605691] BUG: MAX_LOCK_DEPTH too low!
[
|
| I didn't hear any objections so here is the patch again.
|
| [SNMP]: Fix SNMP counters with PREEMPT
|
I don't feel competent to say whether this is correct, but it seems that
this is going a long way towards resolving older problems with the SNMP
counters.
What I can say is that a year
The usage is
# ip link add [name] [device parameters] type veth [peer [name name other
device params]]
This consists of two parts:
1/2 makes some copy-paste changes in ip/iplink.c for generic CLI
attributes parsing,
2/2 the module itself.
Signed-off-by: Pavel Emelyanov [EMAIL PROTECTED]
--
To
From: Pavel Emelyanov [EMAIL PROTECTED]
Date: Thu, 19 Jul 2007 13:32:31 +0400
This routine parses CLI attributes, describing generic link
parameters such as name, address, etc.
This is mostly copy-pasted from iplink_modify().
Signed-off-by: Pavel Emelyanov [EMAIL PROTECTED]
Acked-by: Patrick
module link_veth
Signed-off-by: Vitaliy Gusev [EMAIL PROTECTED]
---
link_veth.c | 76 +++-
veth.h |2 -
2 files changed, 25 insertions(+), 53 deletions(-)
diff --git a/ip/link_veth.c b/ip/link_veth.c
index a4764f2..226b4ef
The do_setlink() function is protected by rtnl, additional locks are
unnecessary.
and the set_operstate() function is called from protected parts. Locks removed
from both functions.
The set_operstate() is also called from rtnl_create_link() and from no other
places.
In rtnl_create_link() none
Interfaces can be grouped and each group has an unique positive integer ID.
It can be set via ip link. Symbolic names can be specified in
/etc/iproute2/rt_ifgroup. Any value of unsigned int32 is valid.
Signed-off-by: Laszlo Attila Toth [EMAIL PROTECTED]
---
include/linux/if_link.h |2 +
In do_setlink() a single notification is sent at the end of the function
if any modification occured. If the address has been changed, another
notification is sent.
Both of them is required because originally only the NETDEV_CHANGEADDR
notification
was sent and although device state change
I think in theory all eapol frames are sent to the PAE group address,
but I have no idea which of the checks would be more efficient. It seems
that the first could be optimised a lot because it's constant too...
They are not.. PAE group address is used for all EAPOL frames in
non-shared
[CCID3]: Whitespace cleanups and outdated documentation
This removes outdated documentation which had been forgotten to be
removed (x_recv, rtt now appear twice, p was removed from rx_sock);
and removes new whitespace.
Signed-off-by: Gerrit Renker [EMAIL PROTECTED]
---
net/dccp/ccids/ccid3.c |
Unfortunately not. Does that really matter? It seems that the
verification whether the frame was encrypted would either be always
require encryption when pairwise keys in use (which this patch doesn't
do right now but could trivially be done) or simply don't care since it
doesn't really
On Tue, Dec 18, 2007 at 11:43:44AM +, Gerrit Renker wrote:
It looks as if this work is reaching the cause of the problem, which would
be good since the problem propagates to all users of such counters (UDP,
UDP-Lite, and similar MIB counters). So thank you for taking this issue up,
I hope
At the beginning - kernel is with gentoo patched, but i checked, there is
nothing major and almost none from patched code used on this router (there is
almost no networking patches, except e1000e support, small GRE fix and few
wireless things, which is not used).
syslog
A number of years ago I had written a comprehensive system monitoring
tool called collectl, which among other things allowed me to monitor
network traffic in real-time display as well as log the data to a file.
Furthermore, that file can be generated in a format suitable for
plotting with
From: Poonam Aggrwal [EMAIL PROTECTED]
This patch makes necessary changes in the QE and UCC framework to support
TDM. It also adds support to configure the BRG properly through device
tree entries. Includes the device tree changes for UCC TDM driver as well.
It also includes device tree entries
Em Tue, Dec 18, 2007 at 12:41:08PM +, Gerrit Renker escreveu:
[CCID3]: Whitespace cleanups and outdated documentation
This removes outdated documentation which had been forgotten to be
removed (x_recv, rtt now appear twice, p was removed from rx_sock);
and removes new whitespace.
On Mon, Dec 17, 2007 at 08:48:03PM -0800, Joe Perches wrote:
diff --git a/MAINTAINERS b/MAINTAINERS
index 9507b42..690f172 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -3758,13 +3758,6 @@ W:
http://www.kernel.org/pub/linux/kernel/people/bunk/trivial/
T: git
On Mon, Dec 17, 2007 at 11:06:04AM +0100, Bernard Pidoux F6BVP wrote:
Hi,
When I killall kissattach I can see the following message.
This happens on kernel 2.6.24-rc5 already patched with the 6 previously
patches I sent recently.
===
[
From: Timo Teras [EMAIL PROTECTED]
Make both send and receive paths use consistently skb-*_header:
mac_header = outer IPv4 header
network_header = encapsulated packet (e.g. inner IPv4 header)
Signed-off-by: Timo Teras [EMAIL PROTECTED]
---
Currently in send path:
network_header = outer
I have only seen this happen once, and cannot reproduce it. I'll keep
trying, though.
Dec 16 22:10:48 syntropy kernel: [ 231.718023]
===
Dec 16 22:10:48 syntropy kernel: [ 231.718025] [ INFO: possible
circular locking dependency detected ]
On Tue, 2007-12-18 at 09:03 -0500, Miles Lane wrote:
I have only seen this happen once, and cannot reproduce it. I'll keep
trying, though.
Dec 16 22:10:48 syntropy kernel: [ 231.718023]
===
Do you have a version that isn't line-wrapped
On Wed, 2007-12-12 at 19:24 +0100, Johannes Berg wrote:
[comments welcome. I really need a refresher on what the frame formats
mean but I think I did the right thing with skb-protocol here, I also
think we had a bug with rfc2042 header frames bigger than 15xx bytes and
eth_type_trans()]
I
This patch makes mac80211 warn (once) when the driver passes up a
frame in which the payload data is not aligned on a four-byte
boundary, with a long comment for people who run into the condition
and need to know what to do.
Signed-off-by: Johannes Berg [EMAIL PROTECTED]
---
net/mac80211/rx.c |
* Mark Seger [EMAIL PROTECTED] 2007-12-18 08:37
Anyhow, I just wanted to let people know that ALL tools that monitor
once a second on older counters will get the wrong numbers and tools
that correct for the wrong number by using fractional intervals (and I
suspect mine is the only one that
Sorry. GMail doesn't support sending unwrapped text, as far as I can
tell. I will send the log segment to you as an attachment. Also,
when I sent my .config inline to Andrew recently, it tripped his spam
filter. I'll attach it as well.
Thanks. This is a bug in iwlwifi.
The problem is
Herbert Xu wrote:
Chris Friesen [EMAIL PROTECTED] wrote:
However, if I specifically try to print out one of the missing entries,
it shows up:
[EMAIL PROTECTED]:/root /tmp/ip neigh show 192.168.24.81
192.168.24.81 dev bond2 lladdr 00:01:af:14:e9:8a REACHABLE
What about
ip -4 neigh
On Sun, 16 Dec 2007 12:37:25 +0100
Gregory CLEMENT [EMAIL PROTECTED] wrote:
Haavard Skinnemoen a écrit :
But the patch is a bit mangled, so I don't think it will apply. Please
have a look in Documentation/email-clients.txt for information on how
to set up Thunderbird to avoid this.
I
On Mon, 17 Dec 2007 18:20:14 -0500
Jeff Garzik wrote:
Jochen Friedrich wrote:
This patch adds support to use the fixed-link property
of an ethernet node to fs_enet for the
CONFIG_PPC_CPM_NEW_BINDING case.
Signed-off-by: Jochen Friedrich [EMAIL PROTECTED]
Acked-by: Vitaly Bordug [EMAIL
Thomas Graf wrote:
* Mark Seger [EMAIL PROTECTED] 2007-12-18 08:37
Anyhow, I just wanted to let people know that ALL tools that monitor
once a second on older counters will get the wrong numbers and tools
that correct for the wrong number by using fractional intervals (and I
suspect mine
On Mon, 17 Dec 2007 20:28:00 -0800
Andrew Morton [EMAIL PROTECTED] wrote:
btw, I cheerfully skipped all your spelling-fixes patches. Some will
have stuck via subsystem maintainers but I have a secret no spelling
fixes unless they're end-user-visible policy. That means I'll take
spelling
On Thu, 13 Dec 2007 02:40:50 PST, Andrew Morton said:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.24-rc5/2.6.24-rc5-mm1/
git-net.patch (I'm guessing one of Daniel's commits, but not sure which one)
causes some complaints:
LD vmlinux.o
MODPOST vmlinux.o
WARNING:
Hello everybody.
I'm experimenting a pretty strange ipsec problem with 2.6.23.x
and openswan 2.4.11
Here is the output from 'ip -s x p':
src 172.16.0.0/23 dst 192.168.15.2/32 uid 0
dir out action allow index 529 priority 2368 ptype main share
any flag 0x00
00
lifetime config:
[EMAIL PROTECTED] wrote:
On Thu, 13 Dec 2007 02:40:50 PST, Andrew Morton said:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.24-rc5/2.6.24-rc5-mm1/
git-net.patch (I'm guessing one of Daniel's commits, but not sure which one)
causes some complaints:
LD vmlinux.o
This patch adds support to use the fixed-link property
of an ethernet node to fs_enet for the
CONFIG_PPC_CPM_NEW_BINDING case.
Signed-off-by: Jochen Friedrich [EMAIL PROTECTED]
Acked-by: Jeff Garzik [EMAIL PROTECTED]
Acked-by: Vitali Bordug [EMAIL PROTECTED]
---
On Sunday 09 December 2007 10:43:56 pm Herbert Xu wrote:
On Mon, Dec 10, 2007 at 04:16:36AM +0100, Patrick McHardy wrote:
Won't this break with manually installed SAs (without a keying
daemon)?
Well what's being suggested here will already break that anyway :)
Alternatively we can take
This patch makes necessary changes in the Neptune driver to support
the new Marvell PHY. It also adds support for the LED blinking
on Neptune cards with Marvell PHY.
diff -uprN -X linux-2.6/Documentation/dontdiff
linux-2.6/drivers/net/niu.c linux-2.6-changed/drivers/net/niu.c
---
On Tue, 2007-12-18 at 06:43 -0700, Matthew Wilcox wrote:
On Mon, Dec 17, 2007 at 08:48:03PM -0800, Joe Perches wrote:
diff --git a/MAINTAINERS b/MAINTAINERS
index 9507b42..690f172 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -3758,13 +3758,6 @@ W:
Hello,
I really apologize for not replying to this mail sooner.
Herbert Xu wrote:
On Mon, Dec 03, 2007 at 07:10:45PM -0500, Hideo AOKI wrote:
Because we have to call wmem_schedule function in ip_append_data()
which is used by several protocols both stream and datagram.
I just thought adding
Denys Fedoryshchenko wrote:
At the beginning - kernel is with gentoo patched, but i checked, there is
nothing major and almost none from patched code used on this router (there is
almost no networking patches, except e1000e support, small GRE fix and few
wireless things, which is not used).
On Fri, 14 Dec 2007, Andy Gospodarek wrote:
On Fri, Dec 14, 2007 at 07:57:42PM +0100, Krzysztof Oledzki wrote:
On Fri, 14 Dec 2007, Andy Gospodarek wrote:
On Fri, Dec 14, 2007 at 05:14:57PM +0100, Krzysztof Oledzki wrote:
On Wed, 12 Dec 2007, Jay Vosburgh wrote:
Herbert Xu [EMAIL
James Nichols a écrit :
Well... please dont start a flame war :(
Back to your SYN_SENT problem, I suppose the remote IP is known, so you
probably could post here the result of a tcdpump ?
tcpdump -p -n -s 1600 host IP_of_problematic_peer -c 500
Most probably remote peer received too many
The last attempt didn't take account of the situation where a timestamp
wasn't available and tcp_clean_rtx_queue() has to feed both the RTO and the
congestion avoidance. This updated patch stores both RTTs, making the
delayed one available for the RTO and the other (ca_seq_rtt) available for
Trying to connect() to an IPv6 link-local multicast address by
specifying the outgoing multicast interface doesn't work, you have to
bind to a device first with an SO_BINDTODEVICE setsockopt() call. This
patch allows the IPV6_MULTICAST_IF setting to also control which
interface should be used
On Dec 18 2007 21:37, Eric Dumazet wrote:
If turning off tcp_sack makes the problem go away, why dont you
turn it off all the time ?
That would just be workaround. I welcome the efforts to track this;
not all users have the time to do so.
Disabling tcp_sack also disabled it kernel-wide,
Brian Haley [EMAIL PROTECTED] wrote on 12/18/2007 12:57:54 PM:
Trying to connect() to an IPv6 link-local multicast address by
specifying the outgoing multicast interface doesn't work, you have to
bind to a device first with an SO_BINDTODEVICE setsockopt() call.
No, you simply have to
On Tue, Dec 18, 2007 at 10:12:31PM +0100, Pidoux wrote:
Hi,
Thank you Jarek for the analysis of the circular locking dependency report.
I applied the patch you proposed and it works well as soon as I am able to
reboot now without
lock warning message and I can also killall kissattach.
I
Looks pretty decent. Main comments (style mostly, driver operation path
seems sound):
* kill the bitfields and unions [in descriptor structs]. they are not
endian-safe as presented, generate poor code, and are otherwise undesirable.
* the basic operations are too verbose:
David Stevens wrote:
Brian Haley [EMAIL PROTECTED] wrote on 12/18/2007 12:57:54 PM:
Trying to connect() to an IPv6 link-local multicast address by
specifying the outgoing multicast interface doesn't work, you have to
bind to a device first with an SO_BINDTODEVICE setsockopt() call.
Other
From:
https://bugzilla.redhat.com/show_bug.cgi?id=426164
kernel version is 2.6.24-0.107.rc5.git3.fc9
From boot log on serial console:
(full log attached)
Added VLAN with VID == 2 to IF -:eth0.1568:-
=
[ INFO: possible recursive locking detected ]
Brian,
OK, I see what you're trying to fix now.
I think the scope_id checks are not quite right-- they
should be something like this:
if (addr_typeIPV6_ADDR_LINKLOCAL) {
if (addr_len = sizeof(struct sockaddr_in6)) {
if (sk-sk_bound_dev_if usin-sin6_scope_id
Thomas Bogendoerfer wrote:
On Mon, Dec 17, 2007 at 08:18:38PM -0500, Jeff Garzik wrote:
Changes to last version:
- Use inline functions for dma_sync_* instead of macros (suggested by Ralf)
- added Kconfig change to make selection for similair SGI boxes easier
hrm, could you rediff? it doesn't
Reduces the number of wakeups from idle per second, makes powertop happy.
Signed-off-by: Parag Warudkar [EMAIL PROTECTED]
--- linux-2.6/net/sched/sch_generic.c 2007-12-07 10:04:43.0 -0500
+++ linux-2.6-work/net/sched/sch_generic.c 2007-12-16 17:57:05.0
-0500
@@ -213,7
sky2 can use deferrable timer for watchdog - reduces wakeups from idle per
second.
Signed-off-by: Parag Warudkar [EMAIL PROTECTED]
--- linux-2.6/drivers/net/sky2.c2007-12-07 10:04:39.0 -0500
+++ linux-2.6-work/drivers/net/sky2.c 2007-12-18 20:07:58.0 -0500
@@
On Tue, Dec 18, 2007 at 08:52:01AM -0600, Chris Friesen wrote:
Looks like that did it. Why does specifying the family make a difference?
Because this is the only parameter that changes kernel behaviour.
Next step is to strace both commands with -s 16384 to see exactly
what the kernel reply
Use deferrable timer for watchdog. Reduces wakeups from idle per second.
Signed-off-by: Parag Warudkar [EMAIL PROTECTED]
--- linux-2.6/drivers/net/e1000/e1000_main.c2007-12-07 10:04:39.0
-0500
+++ linux-2.6-work/drivers/net/e1000/e1000_main.c 2007-12-18
20:38:38.0
Reduce wakeups from idle per second.
Signed-off-by: Parag Warudkar [EMAIL PROTECTED]
--- linux-2.6/drivers/net/e1000e/netdev.c 2007-12-07 10:04:39.0
-0500
+++ linux-2.6-work/drivers/net/e1000e/netdev.c 2007-12-18 20:45:59.0
-0500
@@ -3899,7 +3899,7 @@
The net flow hash randomization timer runs every 10 minutes.
This time is low priority and doesn't need to wakeup the CPU.
Signed-off-by: Stephen Hemminger [EMAIL PROTECTED]
--- a/net/core/flow.c 2007-12-18 07:43:31.0 -0800
+++ b/net/core/flow.c 2007-12-18 07:44:32.0 -0800
@@
The neighbor GC timer runs once a second, but it doesn't need to wake
up the machine.
Signed-off-by: Stephen Hemminger [EMAIL PROTECTED]
--- a/net/core/neighbour.c 2007-12-18 07:46:07.0 -0800
+++ b/net/core/neighbour.c 2007-12-18 07:47:36.0 -0800
@@ -270,7 +270,7 @@
On Tue, 2007-12-18 at 15:57 +0100, Johannes Berg wrote:
Thanks. This is a bug in iwlwifi.
The problem is actually another case where my workqueue debugging with
lockdep is triggering a warning :))
Here's the thing:
iwl3945_cancel_deferred_work does
Hello,
I would like to update this patch since there were redundant extern
declarations.
Regards,
Hideo
---
This patch includes changes in network core sub system for memory
accounting.
Memory scheduling, charging, uncharging and reclaiming functions are
added. These functions use
Hi Ingo:
I noticed that local_bh_disable is now always out-of-line. The
change was made when TRACE_IRQFLAGS was added. However, with
TRACE_IRQFLAGS off, local_bh_disable does exactly the same work
as before. In particular, it does pretty much the same as what
preempt_disable does and the
On Wed, Dec 19, 2007 at 02:10:34PM +0900, Kazunori MIYAZAWA wrote:
Dec 19 11:31:44 hawaii kernel: ip6_rcv_finish: head=f7505000(**)
Dec 19 11:31:44 hawaii kernel: ip6_rcv_finish: data=f7505020(**)
Dec 19 11:31:44 hawaii kernel: xfrm6_tunnel_output: head=f7505000
Dec 19 11:31:44 hawaii kernel:
From: Herbert Xu [EMAIL PROTECTED]
Date: Wed, 19 Dec 2007 14:12:10 +0800
[IPSEC]: Do xfrm_state_check_space before encapsulation
While merging the IPsec output path I moved the encapsulation output
operation to the top of the loop so that it sits outside of the locked
section.
Rereading the thread it's unclear to me which solution was deemed correct.
I'm not a big fan of fiddling/forcing SA lifetimes unless we have no other
option; if someone is foolish enough to use manual keying with replay
protection and no mechanism to catch rollover then they most likely have
Hi Dave:
[IPSEC]: Rename tunnel-mode functions to avoid collisions with tunnels
It appears that I've managed to create two different functions both
called xfrm6_tunnel_output. This is because we have the plain tunnel
encapsulation named xfrmX_tunnel as well as the tunnel-mode encapsulation
Marco Berizzi [EMAIL PROTECTED] wrote:
Hello everybody.
I'm experimenting a pretty strange ipsec problem with 2.6.23.x
and openswan 2.4.11
Here is the output from 'ip -s x p':
It's a bug in openswan but I haven't had the time to track it
down yet. Anyway, the kernel is not involved since the
Stephen Hemminger a écrit :
The neighbor GC timer runs once a second, but it doesn't need to wake
up the machine.
Signed-off-by: Stephen Hemminger [EMAIL PROTECTED]
--- a/net/core/neighbour.c 2007-12-18 07:46:07.0 -0800
+++ b/net/core/neighbour.c 2007-12-18 07:47:36.0
71 matches
Mail list logo
