From: Adrian Bunk [EMAIL PROTECTED]
Date: Mon, 12 Nov 2007 08:58:36 +0100
On Sun, Nov 11, 2007 at 04:09:40PM +0900, Simon Horman wrote:
On Sun, Nov 11, 2007 at 07:48:40AM +0100, Adrian Bunk wrote:
This patch removes the following unused EXPORT_SYMBOL's:
- ip_vs_try_bind_dest
-
David Miller wrote:
From: Pavel Emelyanov [EMAIL PROTECTED]
Date: Sat, 10 Nov 2007 17:32:58 +0300
The inetpeer.c tracks the LRU list of inet_perr-s, but makes
it by hands. Use the list_head-s for this.
Signed-off-by: Pavel Emelyanov [EMAIL PROTECTED]
This makes every inetpeer struct
From: Pavel Emelyanov [EMAIL PROTECTED]
Date: Mon, 12 Nov 2007 11:57:23 +0300
No. I remove _two_ pointers unused_next and unused_prevp, and add
the list_head, which is _two_ pointers as well. I've even checked the
compilation on both i386 and x86_64 - the sizeof(struct inet_peer)
is not
Trond Myklebust [EMAIL PROTECTED] wrote:
take a SHUT_RD/SHUT_WR/SHUT_RDWR argument instead of the
Hmmm... Why SHUT_*? Why not SHUTDOWN_*?
David
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Mon, 2007-11-12 at 12:22 +, David Howells wrote:
Trond Myklebust [EMAIL PROTECTED] wrote:
take a SHUT_RD/SHUT_WR/SHUT_RDWR argument instead of the
Hmmm... Why SHUT_*? Why not SHUTDOWN_*?
SHUT_RD/SHUT_WR/SHUT_RDWR are the traditional names for these constants
(see 'man 3
The inetpeer.c tracks the LRU list of inet_perr-s, but makes
it by hands. Use the list_head-s for this.
Signed-off-by: Pavel Emelyanov [EMAIL PROTECTED]
---
diff --git a/include/net/inetpeer.h b/include/net/inetpeer.h
index aa10a81..ad8404b 100644
--- a/include/net/inetpeer.h
+++
Trond Myklebust [EMAIL PROTECTED] wrote:
SHUT_RD/SHUT_WR/SHUT_RDWR are the traditional names for these constants
(see 'man 3 shutdown') and so should be easier to remember.
Good point.
David
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL
Jesper Juhl wrote:
From: Jesper Juhl [EMAIL PROTECTED]
In net/sctp/sm_statefuns.c::sctp_sf_abort_violation() we may leak
the storage allocated for 'abort' by returning from the function
without using or freeing it. This happens in case
sctp_auth_recv_cid(SCTP_CID_ABORT, asoc) is true and
The loopback is now dynamically allocated. The ipv6 code was written
considering the loopback is allocated before the ipv6 protocol
initialization. This is still the case when we don't use multiple
network namespaces.
In the case of the network namespaces, ipv6 notification handler is
already
Dear all,
I'm writing a network analyzer software using Linux and I need a VERY
precise frame time stamping. Therefor I am planing to add my own time
stamping algorithm on a modified network driver. For test purpose I
did so :
skb-tstamp.tv64 = 0x00010002;
netif_rx(skb);
On the
Daniel Lezcano wrote:
The loopback is now dynamically allocated. The ipv6 code was written
considering the loopback is allocated before the ipv6 protocol
initialization. This is still the case when we don't use multiple
network namespaces.
In the case of the network namespaces, ipv6
Denis V. Lunev wrote:
Daniel Lezcano wrote:
The loopback is now dynamically allocated. The ipv6 code was written
considering the loopback is allocated before the ipv6 protocol
initialization. This is still the case when we don't use multiple
network namespaces.
In the case of the network
Hi,
As reported last week by Or Gerlitz and confirmed by me, there is a kernel
crash
when trying to unenslave all ib slaves (which leads to bonding master
destruction).
I also found that it happens with Ethernet slaves if following the steps:
1. unenslaving all slaves via sysfs
2. deleting
Hi David
I've updated the series of SCTP bugfixes. These pass all of the regression
tests.
You can pull the changes from:
master.kernel.org:/pub/scm/linux/kernel/git/vxy/lksctp-dev.git pending
Summary of changes:
Jesper Juhl (1):
Fix memory leak in discard case of
From: Wei Yongjun [EMAIL PROTECTED]
Just fix the bad format of the comment in outqueue.c.
Signed-off-by: Wei Yongjun [EMAIL PROTECTED]
Signed-off-by: Vlad Yasevich [EMAIL PROTECTED]
---
net/sctp/outqueue.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git
After learning more about rcu, it looks like the ADD-IP hadling
doesn't need to call call_rcu_bh. All the rcu critical sections
use rcu_read_lock, so using call_rcu_bh is wrong here.
Now, restore the local_bh_disable() code blocks and use normal
call_rcu() calls. Also restore the missing return
Commit d0ce92910bc04e107b2f3f2048f07e94f570035d broke several retransmit
cases including fast retransmit. The reason is that we should
only delay by rto while doing retranmists as a result of a timeout.
Retransmit as a result of path mtu discover, fast retransmit, or
other evernts that should
There is a possible race condition where the timer code will
free the association and the next packet in the queue will also
attempt to free the same association.
The example is, when we receive an ABORT at about the same time
as the retransmission timer fires. If the timer wins the race,
it
This patch adds a tunable that will allow ADD_IP to work without
AUTH for backward compatibility. The default value is off since
the default value for ADD_IP is off as well. People who need
to use ADD-IP with older implementations take risks of connection
hijacking and should consider upgrading
Signed-off-by: Vlad Yasevich [EMAIL PROTECTED]
---
include/net/sctp/structs.h |1 -
net/sctp/associola.c |2 +-
net/sctp/sm_make_chunk.c |5 +++--
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/include/net/sctp/structs.h b/include/net/sctp/structs.h
index
A SCTP endpoint may have a lot of associations on them and walking
the list is fairly inefficient. Instead, use a hashed lookup,
and filter out the hash list based on the endopoing we already have.
Signed-off-by: Vlad Yasevich [EMAIL PROTECTED]
---
net/sctp/endpointola.c | 34
From: Wei Yongjun [EMAIL PROTECTED]
If ASCONF chunk is bundled with other chunks as the first chunk, when
process the ASCONF parameters, full packet data will be process as the
parameters of the ASCONF chunk, not only the real parameters. So if you
send a ASCONF chunk bundled with other chunks,
Convert the custom hash list traversals to use hlist functions.
Signed-off-by: Vlad Yasevich [EMAIL PROTECTED]
---
include/net/sctp/sctp.h|3 +++
include/net/sctp/structs.h | 10 --
net/sctp/endpointola.c |3 ++-
net/sctp/input.c | 43
There is a small bug when we process a FWD-TSN. We'll deliver
anything upto the current next expected SSN. However, if the
next expected is already in the queue, it will take another
chunk to trigger its delivery. The fix is to simply check
the current queued SSN is the next expected one.
When the code calls uncork, trigger a queue flush, even
if the queue was not corked. Most callers that explicitely
cork the queue will have additinal checks to see if they
corked it. Callers who do not cork the queue expect packets
to flow when they call uncork.
The scneario that showcased this
From: Jesper Juhl [EMAIL PROTECTED]
In net/sctp/sm_statefuns.c::sctp_sf_abort_violation() we may leak
the storage allocated for 'abort' by returning from the function
without using or freeing it. This happens in case
sctp_auth_recv_cid(SCTP_CID_ABORT, asoc) is true and we jump to
the 'discard'
Signed-off-by: Vlad Yasevich [EMAIL PROTECTED]
---
include/net/sctp/sctp.h |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/include/net/sctp/sctp.h b/include/net/sctp/sctp.h
index 67c997c..34318a3 100644
--- a/include/net/sctp/sctp.h
+++ b/include/net/sctp/sctp.h
@@ -65,7
SCTP-AUTH and future ADD-IP updates have a requirement to
do additional verification of parameters and an ability to
ABORT the association if verification fails. So, introduce
additional return code so that we can clear signal a required
action.
Signed-off-by: Vlad Yasevich [EMAIL PROTECTED]
---
Daniel Lezcano [EMAIL PROTECTED] writes:
The loopback is now dynamically allocated. The ipv6 code was written
considering the loopback is allocated before the ipv6 protocol
initialization. This is still the case when we don't use multiple
network namespaces.
You do know that
why should we care on down? we are destroying the device. It should
gone. All references to it should also gone. So, we should perform the
cleaning and remove all IPv6 addresses, so notifier should also work.
We need to take care of netdev down, someone can put the loopback down
if he
On Mon, 12 Nov 2007 16:42:34 +0100
Antoine Zen-Ruffinen [EMAIL PROTECTED] wrote:
Dear all,
I'm writing a network analyzer software using Linux and I need a VERY
precise frame time stamping. Therefor I am planing to add my own time
stamping algorithm on a modified network driver. For test
Denis V. Lunev [EMAIL PROTECTED] writes:
Index: linux-2.6-netns/net/ipv6/addrconf.c
===
--- linux-2.6-netns.orig/net/ipv6/addrconf.c
+++ linux-2.6-netns/net/ipv6/addrconf.c
@@ -2272,7 +2272,8 @@ static int addrconf_notify(struct
Denis V. Lunev [EMAIL PROTECTED] writes:
why should we care on down? we are destroying the device. It should
gone. All references to it should also gone. So, we should perform the
cleaning and remove all IPv6 addresses, so notifier should also work.
We need to take care of netdev down,
Eric W. Biederman wrote:
Denis V. Lunev [EMAIL PROTECTED] writes:
Index: linux-2.6-netns/net/ipv6/addrconf.c
===
--- linux-2.6-netns.orig/net/ipv6/addrconf.c
+++ linux-2.6-netns/net/ipv6/addrconf.c
@@ -2272,7 +2272,8 @@ static int
Joonwoo Park wrote:
IMHO even though netdevice is in the promiscuous mode, we should receive all
of ingress packets.
This disable the vlan filtering feature when a vlan hw accel configured e1000
device goes into promiscuous mode.
This make packets visible to sniffers though it's not vlan id
Kok, Auke wrote:
Joonwoo Park wrote:
IMHO even though netdevice is in the promiscuous mode, we should receive all of
ingress packets.
This disable the vlan filtering feature when a vlan hw accel configured e1000
device goes into promiscuous mode.
This make packets visible to sniffers though
Commit bea3348e (the NAPI changes) made sungem unconditionally enable
NAPI when resuming and unconditionally disable when suspending, this,
however, makes napi_disable() hang when suspending when the interface
was taken down before suspend because taking the interface down also
disables NAPI. This
From: Fred L. Templin [EMAIL PROTECTED]
This message attaches the combined diffs from
messages 01/05 through 04/05. This file should be
suitable for use with the patch utility.
Signed-off-by: Fred L. Templin [EMAIL PROTECTED]
--- linux-2.6.24-rc2/include/linux/if.h.orig2007-11-08
From: Fred L. Templin [EMAIL PROTECTED]
This is experimental support for the Intra-Site Automatic
Tunnel Addressing Protocol (ISATAP) per RFC4214. It uses
the SIT module, and is configured using the unmodified
ip utility with device names beginning with: isatap.
The following diffs are specific
From: Fred L. Templin [EMAIL PROTECTED]
This is experimental support for the Intra-Site Automatic
Tunnel Addressing Protocol (ISATAP) per RFC4214. It uses
the SIT module, and is configured using the unmodified
ip utility with device names beginning with: isatap.
The following diffs are specific
From: Fred L. Templin [EMAIL PROTECTED]
This is experimental support for the Intra-Site Automatic
Tunnel Addressing Protocol (ISATAP) per RFC4214. The
attached file includes diffs that are specific to the
iproute2-2.6.23 software distribution.
Signed-off-by: Fred L. Templin [EMAIL PROTECTED]
---
Patrick McHardy wrote:
Kok, Auke wrote:
Joonwoo Park wrote:
IMHO even though netdevice is in the promiscuous mode, we should receive
all of ingress packets.
This disable the vlan filtering feature when a vlan hw accel configured
e1000 device goes into promiscuous mode.
This make packets
On Thu, 2007-11-08 at 23:49 +0100, Rafael J. Wysocki wrote:
On Thursday, 8 of November 2007, Grant Wilson wrote:
On Thu, 8 Nov 2007 22:42:21 +0100
Rafael J. Wysocki [EMAIL PROTECTED] wrote:
On Thursday, 8 of November 2007, Grant Wilson wrote:
On Thu, 8 Nov 2007 16:53:10 +0100
From: Fred L. Templin [EMAIL PROTECTED]
This is experimental support for the Intra-Site Automatic
Tunnel Addressing Protocol (ISATAP) per RFC4214. It uses
the SIT module, and is configured using the unmodified
ip utility with device names beginning with: isatap.
The following diffs are specific
From: Fred L. Templin [EMAIL PROTECTED]
This is experimental support for the Intra-Site Automatic
Tunnel Addressing Protocol (ISATAP) per RFC4214. It uses
the SIT module, and is configured using the unmodified
ip utility with device names beginning with: isatap.
The following diffs are specific
Coalesce setting errors use the same error messages as the
descriptor ring errors.
Signed-off-by: Auke Kok [EMAIL PROTECTED]
---
ethtool.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/ethtool.c b/ethtool.c
index 6c7a2e3..bb9dd59 100644
--- a/ethtool.c
+++
On Mon, 12 Nov 2007 19:05:49 +0100
Peter Zijlstra [EMAIL PROTECTED] wrote:
On Thu, 2007-11-08 at 23:49 +0100, Rafael J. Wysocki wrote:
On Thursday, 8 of November 2007, Grant Wilson wrote:
On Thu, 8 Nov 2007 22:42:21 +0100
Rafael J. Wysocki [EMAIL PROTECTED] wrote:
On Thursday,
From: Fred L. Templin [EMAIL PROTECTED]
This is experimental support for the Intra-Site Automatic
Tunnel Addressing Protocol (ISATAP) per RFC4214. It uses
the SIT module, and is configured using the unmodified
ip utility with device names beginning with: isatap.
The following diffs are specific
Hi,
I'm trying to get the ULI 526x driver working on a Freescale 8610 reference
board, and it can't connect. When I turn on debug, I see this:
Configuring network interfaces...uli526x: uli526x_open 0
uli526x: uli526x_init() 0
uli526x: uli526x_descriptor_init() 0
uli526x: send_filter_frame()
Timur Tabi wrote:
Hi,
I'm trying to get the ULI 526x driver working on a Freescale 8610
reference board, and it can't connect. When I turn on debug, I see this:
Update: I can ping anything on my subnet, but nothing else. Also, it looks like
my MAC address is hosed:
eth0 Link
Daniel Lezcano [EMAIL PROTECTED] writes:
Eric W. Biederman wrote:
Denis V. Lunev [EMAIL PROTECTED] writes:
Index: linux-2.6-netns/net/ipv6/addrconf.c
===
--- linux-2.6-netns.orig/net/ipv6/addrconf.c
+++
From: Fred L. Templin [EMAIL PROTECTED]
This message attaches the combined diffs from
messages 01/05 through 04/05. This file should be
suitable for use with the patch utility.
Signed-off-by: Fred L. Templin [EMAIL PROTECTED]
---
--- linux-2.6.24-rc2/include/linux/if.h.orig2007-11-08
...and fix a couple of bugs in the NBD, CIFS and OCFS2 socket handlers.
Looking at the sock-op-shutdown() handlers, it looks as if all of them
take a SHUT_RD/SHUT_WR/SHUT_RDWR argument instead of the
RCV_SHUTDOWN/SEND_SHUTDOWN arguments.
Add a helper, and then define the SHUT_* enum to ensure
Let me try to clarify:
* when the init network namespace is created, the loopback is created
first, before ipv6, and the notifier call chain for ipv6 is not setup,
so the protocol does not receive the REGISTER event
* when the init network namespace is destroyed during shutdown, the
-Original Message-
From: osprey67 [mailto:[EMAIL PROTECTED]
Sent: Monday, November 12, 2007 7:54 AM
To: netdev@vger.kernel.org
Subject: [PATCH 01/05] ipv6: RFC4214 Support (4)
From: Fred L. Templin [EMAIL PROTECTED]
This is experimental support for the Intra-Site Automatic
Tunnel
-Original Message-
From: osprey67 [mailto:[EMAIL PROTECTED]
Sent: Monday, November 12, 2007 7:55 AM
To: netdev@vger.kernel.org
Subject: [PATCH 03/05] ipv6: RFC4214 Support (4)
From: Fred L. Templin [EMAIL PROTECTED]
This is experimental support for the Intra-Site Automatic
Tunnel
-Original Message-
From: osprey67 [mailto:[EMAIL PROTECTED]
Sent: Monday, November 12, 2007 7:55 AM
To: netdev@vger.kernel.org
Subject: [PATCH 02/05] ipv6: RFC4214 Support (4)
From: Fred L. Templin [EMAIL PROTECTED]
This is experimental support for the Intra-Site Automatic
Tunnel
-Original Message-
From: osprey67 [mailto:[EMAIL PROTECTED]
Sent: Monday, November 12, 2007 7:58 AM
To: netdev@vger.kernel.org
Subject: [PATCH 01/01] iproute2-2.6.23: RFC4214 Support (4)
From: Fred L. Templin [EMAIL PROTECTED]
This is experimental support for the Intra-Site Automatic
-Original Message-
From: osprey67 [mailto:[EMAIL PROTECTED]
Sent: Monday, November 12, 2007 7:54 AM
To: netdev@vger.kernel.org
Subject: [PATCH 01/05] ipv6: RFC4214 Support (4)
From: Fred L. Templin [EMAIL PROTECTED]
This is experimental support for the Intra-Site Automatic
Tunnel
From: Fred L. Templin [EMAIL PROTECTED]
This is experimental support for the Intra-Site Automatic
Tunnel Addressing Protocol (ISATAP) per RFC4214. It uses
the SIT module, and is configured using extensions to the
iproute2 utility.
The following diffs are specific to the Linux 2.6.24-rc2
kernel
From: Fred L. Templin [EMAIL PROTECTED]
This is experimental support for the Intra-Site Automatic
Tunnel Addressing Protocol (ISATAP) per RFC4214. It uses
the SIT module, and is configured using extensions to the
iproute2 utility.
The following diffs are specific to the Linux 2.6.24-rc2
kernel
From: Fred L. Templin [EMAIL PROTECTED]
This is experimental support for the Intra-Site Automatic
Tunnel Addressing Protocol (ISATAP) per RFC4214. It uses
the SIT module, and is configured using extensions to the
iproute2 utility.
The following diffs are specific to the Linux 2.6.24-rc2
kernel
From: Fred L. Templin [EMAIL PROTECTED]
This is experimental support for the Intra-Site Automatic
Tunnel Addressing Protocol (ISATAP) per RFC4214. It uses
the SIT module, and is configured using extensions to the
iproute2 utility.
The following diffs are specific to the Linux 2.6.24-rc2
kernel
From: Fred L. Templin [EMAIL PROTECTED]
This is experimental support for the Intra-Site Automatic
Tunnel Addressing Protocol (ISATAP) per RFC4214. It uses
the SIT module, and is configured using the unmodified
ip utility with device names beginning with: isatap.
The following diffs are specific
Hi Fred
First, are you breaking up the functionality into multiple
patches _only_ to ease review and plan to submit the final
version as a big patch?
The reason I ask, is that you Patch 02, which adds Kconfig
pieces could break compilations if the functionality is
enabled.
Templin, Fred L
Vlad,
Yes, I was breaking into multiples to ease review only.
The [PATCH 01/04] ... (5) thread includes the complete
reviewable and patchable final text in 4 files. In my
next message, I will put the entire patchfile as inline
text. (The [PATCH 01/01] ... (5) for 'iproute2' is
already complete.)
From: Fred L. Templin [EMAIL PROTECTED]
This is experimental support for the Intra-Site Automatic
Tunnel Addressing Protocol (ISATAP) per RFC4214. It uses
the SIT module, and is configured using extensions to the
iproute2 utility.
The following diffs are specific to the Linux 2.6.24-rc2
kernel
Hi Fred
Templin, Fred L wrote:
Vlad,
Yes, I was breaking into multiples to ease review only.
The [PATCH 01/04] ... (5) thread includes the complete
reviewable and patchable final text in 4 files. In my
next message, I will put the entire patchfile as inline
text. (The [PATCH 01/01] ...
From: Denis V. Lunev [EMAIL PROTECTED]
Date: Mon, 12 Nov 2007 19:49:03 +0300
Unregister for a loopback in !init_net is a _valid_ operation and should
be clean, i.e. without kludges in the path. This is the only way to
check the ref-counting.
For ipv6 the stack really wants to pin down the
Ok, thanks for the explanation. One questions is though why
do we need all the #if defines() throughout the file?
Was just trying to follow what I thought was
convention, but I'm willing to be educated...
Most distros end up enabled almost everything anyway. Looking
at the code, there is
From: Kok, Auke [EMAIL PROTECTED]
Date: Mon, 12 Nov 2007 09:12:40 -0800
Actually I think this patch removes a choice from the user.
Before this patch, the user can sniff all traffic by disabling vlans, or a
specific vlan only by leaving vlans on when going into promisc mode.
After this
On Mon, 2007-11-12 at 18:45 +0100, Johannes Berg wrote:
Commit bea3348e (the NAPI changes) made sungem unconditionally enable
NAPI when resuming and unconditionally disable when suspending, this,
however, makes napi_disable() hang when suspending when the interface
was taken down before
From: Patrick McHardy [EMAIL PROTECTED]
Date: Mon, 12 Nov 2007 18:21:35 +0100
Do you really consider that a realistic choice? Who is going to
remove interfaces that are in use just to see traffic for other
VLANs? Sniffing specific VLANs can always be done on the VLAN
device itself.
Change
David Miller wrote:
When you select VLAN, you by definition are asking for non-VLAN
traffic to be elided. It is like plugging the ethernet cable
into one switch or another.
For max functionality it seems like the raw eth device should show
everything on the wire in promiscuous mode.
If we
Chris Friesen wrote:
David Miller wrote:
When you select VLAN, you by definition are asking for non-VLAN
traffic to be elided. It is like plugging the ethernet cable
into one switch or another.
For max functionality it seems like the raw eth device should show
everything on the wire in
From: Chris Friesen [EMAIL PROTECTED]
Date: Mon, 12 Nov 2007 16:43:24 -0600
David Miller wrote:
When you select VLAN, you by definition are asking for non-VLAN
traffic to be elided. It is like plugging the ethernet cable
into one switch or another.
For max functionality it seems like
On Sun, 2007-11-04 at 09:47 +0200, Eliezer Tamir wrote:
On Fri, 2007-11-02 at 16:35 -0700, Max Asbock wrote:
I built the newest bnx2x code against the net-2.6 kernel and ran a
number of stress tests with netperf and pktgen. I did not encounter
any
errors.
Max
Thanks,
From: Ram Pai [EMAIL PROTECTED]
Date: Mon, 12 Nov 2007 15:13:23 -0800
On Sun, 2007-11-04 at 09:47 +0200, Eliezer Tamir wrote:
On Fri, 2007-11-02 at 16:35 -0700, Max Asbock wrote:
I built the newest bnx2x code against the net-2.6 kernel and ran a
number of stress tests with netperf
From: Fred L. Templin [EMAIL PROTECTED]
This patch includes support for the Intra-Site Automatic Tunnel
Addressing Protocol (ISATAP) per RFC4214. It uses the SIT
module, and is configured using extensions to the iproute2
utility.
The following diffs are specific to the Linux 2.6.24-rc2 kernel
On Mon, Nov 12, 2007 at 02:57:16PM -0800, David Miller wrote:
From: Chris Friesen [EMAIL PROTECTED]
Date: Mon, 12 Nov 2007 16:43:24 -0600
David Miller wrote:
When you select VLAN, you by definition are asking for non-VLAN
traffic to be elided. It is like plugging the ethernet cable
From: Fred L. Templin [EMAIL PROTECTED]
This patch includes support for the Intra-Site Automatic Tunnel
Addressing Protocol (ISATAP) per RFC4214.
The following diffs are specific to the iproute2-2.6.23
software distribution. This message includes the full and
patchable diff text; please use this
From: Willy Tarreau [EMAIL PROTECTED]
Date: Tue, 13 Nov 2007 00:15:16 +0100
I can say that sometimes you'd like to be aware that one of your
VLANs is wrong and you'd simply like to sniff the wire to guess the
correct tag. And on production, you simply cannot remove other
VLANs, otherwise you
This patch adds support for the RDC R6040 MAC we can find in the RDC R-321x
System-on-chips.
Signed-off-by: Sten Wang [EMAIL PROTECTED]
Signed-off-by: Daniel Gimpelevich [EMAIL PROTECTED]
Signed-off-by: Florian Fainelli [EMAIL PROTECTED]
--
diff --git a/drivers/net/Kconfig b/drivers/net/Kconfig
fix sparse warnings Using plain integer as NULL pointer
Signed-off-by: Joe Perches [EMAIL PROTECTED]
---
drivers/net/ppp_async.c | 34 ++--
drivers/net/ppp_generic.c | 126 ++--
drivers/net/ppp_synctty.c | 27 +-
3 files changed,
Willy Tarreau wrote:
On Mon, Nov 12, 2007 at 03:19:23PM -0800, David Miller wrote:
From: Willy Tarreau [EMAIL PROTECTED]
Date: Tue, 13 Nov 2007 00:15:16 +0100
I can say that sometimes you'd like to be aware that one of your
VLANs is wrong and you'd simply like to sniff the wire to guess the
On Sun, 11 Nov 2007 10:52:41 -0800 (PST) [EMAIL PROTECTED] wrote:
The RTNLGRP_ND_USEROPT NetLink message introduced in 2.6.24 does not
seem to include any information as to which netif the user options
come from. Considering this is meant to carry data that is heavily
link-layer involved, this
On Mon, Nov 12, 2007 at 03:19:23PM -0800, David Miller wrote:
From: Willy Tarreau [EMAIL PROTECTED]
Date: Tue, 13 Nov 2007 00:15:16 +0100
I can say that sometimes you'd like to be aware that one of your
VLANs is wrong and you'd simply like to sniff the wire to guess the
correct tag. And
From: Willy Tarreau [EMAIL PROTECTED]
Date: Tue, 13 Nov 2007 00:32:57 +0100
At least, being able to disable the feature at module load time
would be acceptable. Many people who often need to sniff on decent
machines would always keep it disabled.
I'm willing to accept the feature, in whatever
Userland neighbor discovery options are typically heavily involved with
the interface on which thay are received: add a missing ifindex field to
the original struct. Thanks to Rémi Denis-Courmont.
Signed-off-by: Pierre Ynard [EMAIL PROTECTED]
diff --git a/include/linux/rtnetlink.h
From: Pierre Ynard [EMAIL PROTECTED]
Date: Tue, 13 Nov 2007 01:54:13 +0100
Userland neighbor discovery options are typically heavily involved with
the interface on which thay are received: add a missing ifindex field to
the original struct. Thanks to Rémi Denis-Courmont.
Signed-off-by:
From: Pierre Ynard [EMAIL PROTECTED]
Date: Tue, 13 Nov 2007 01:08:26 + (GMT)
Unfortunately you cannot change the layout of a structure
already exported to userspace, it is part of the ABI.
Well, I thought it would not be a problem, as it is not exactly
released yet. We are also
Unfortunately you cannot change the layout of a structure
already exported to userspace, it is part of the ABI.
Well, I thought it would not be a problem, as it is not exactly
released yet. We are also currently developping the
corresponding RDNSS daemon and would be totally ready to
handle
Unfortunately you cannot change the layout of a structure
already exported to userspace, it is part of the ABI.
Well, I thought it would not be a problem, as it is not exactly
released yet. We are also currently developping the
corresponding RDNSS daemon and would be totally ready
2007/11/13, Willy Tarreau [EMAIL PROTECTED]:
On Mon, Nov 12, 2007 at 02:57:16PM -0800, David Miller wrote:
From: Chris Friesen [EMAIL PROTECTED]
Date: Mon, 12 Nov 2007 16:43:24 -0600
David Miller wrote:
When you select VLAN, you by definition are asking for non-VLAN
traffic to
2007/11/13, David Miller [EMAIL PROTECTED]:
From: Willy Tarreau [EMAIL PROTECTED]
Date: Tue, 13 Nov 2007 00:32:57 +0100
At least, being able to disable the feature at module load time
would be acceptable. Many people who often need to sniff on decent
machines would always keep it
You won the sum of 250,000,GBP by the Thunderball promotions. contact this
email for further instructions: [EMAIL PROTECTED]
TEL:+447045708596
Thank you.
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
From: Pierre Ynard [EMAIL PROTECTED]
Date: Tue, 13 Nov 2007 01:19:47 + (GMT)
Unfortunately you cannot change the layout of a structure
already exported to userspace, it is part of the ABI.
Well, I thought it would not be a problem, as it is not exactly
released yet. We are
In article [EMAIL PROTECTED] (at Mon, 12 Nov 2007 12:50:53 -0700), [EMAIL
PROTECTED] (Eric W. Biederman) says:
My opinion is that both your analysis is slightly off (as to the cause
of your problems) and that your approach to fix your problem is wrong
because you don't untangle the knot you
From: Joe Perches [EMAIL PROTECTED]
Date: Mon, 12 Nov 2007 15:33:51 -0800
fix sparse warnings Using plain integer as NULL pointer
Signed-off-by: Joe Perches [EMAIL PROTECTED]
Applied, thanks Joe.
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to
From: Benjamin Herrenschmidt [EMAIL PROTECTED]
Date: Tue, 13 Nov 2007 09:32:46 +1100
On Mon, 2007-11-12 at 18:45 +0100, Johannes Berg wrote:
Commit bea3348e (the NAPI changes) made sungem unconditionally enable
NAPI when resuming and unconditionally disable when suspending, this,
1 - 100 of 128 matches
Mail list logo
