Re: PROBLEM: kernel BUG at net/ipv6/ip6_output.c:718

2006-10-02 Thread Herbert Xu
On Tue, Oct 03, 2006 at 03:49:35PM +1000, Herbert Xu wrote: > > OK, I think I've got the right bug this time. Here is the patch for the other bug that I found along the way: [UDP6]: Fix MSG_PROBE crash UDP tracks corking status through the pending variable. The IP layer also tracks it through t

Re: PROBLEM: kernel BUG at net/ipv6/ip6_output.c:718

2006-10-02 Thread Herbert Xu
On Thu, Sep 28, 2006 at 10:40:18AM +0200, cagri coltekin wrote: > > No. Bug is the first after boot: OK, I think I've got the right bug this time. [UDP6]: Fix flowi clobbering The udp6_sendmsg function uses a shared buffer to store the flow without taking any locks. This leads to races with SMP

[PATCH] bcm43xx-softmac: Fix system hang for x86-64 with >1GB RAM

2006-10-02 Thread Larry Finger
The bcm43xx-softmac software currently fails when running on x86_64 systems with more than 1GB RAM and one of the card variants with 30-bit DMA addressing. This patch uses the address extension bits in the hardware to set the correct DMA mask for the specific card in use. Signed-off-by: Larry Fing

Re: Please pull bcm43xx-d80211 bugfixes and new features

2006-10-02 Thread Larry Finger
Michael Buesch wrote: Hi John, Please pull from my tree git pull http://bu3sch.de/git/wireless-dev.git for-linville This will pull various bugfixes and feature improvements. Most noteably it will pull a bugfix for a crash introduced by an earlier patch to d80211 which changed RX status informat

[PATCH][XFRM] Fixes for net-2.6

2006-10-02 Thread Masahide NAKAMURA
Hello, I have two patches to fix XFRM. Can you check and apply them? HEADLINES - [XFRM] POLICY: Fix per-direction policy counter after flushing. [XFRM] STATE: Use destination address for src hash. DIFFSTAT net/xfrm/xfrm_hash.h |7 --- net/xfrm/xfrm_policy.c

[PATCH] hp100: fix conditional compilation mess

2006-10-02 Thread Jeff Garzik
The previous hp100 changeset attempted to kill warnings, but was only tested on !CONFIG_ISA platforms. The correct conditional compilation setup involves tested CONFIG_ISA rather than just MODULE. Fixes link on CONFIG_ISA platforms (i386) in current -git. Signed-off-by: Jeff Garzik <[EMAIL PROTE

[PATCH 2.6] Fix WE-21 Orinoco overflow issue...

2006-10-02 Thread Jean Tourrilhes
Hi John, This patch fixes the Orinoco driver overflow issue with WE-21. This was discussed on the mailing list, the reporter confirmed that it fixes the issue and Andrew has already added this patch in tree. Regards, Jean --

[PATCH 2.6] More WE-21 potential overflows...

2006-10-02 Thread Jean Tourrilhes
Hi, After the Orinoco issue, I did an audit of other drivers for the same issue. Three drivers were NULL terminating the ESSID, which could cause an overflow in WE-21 when the ESSID has maximum size. Sorry for having overlooked that... Jean Signed-off-by: Jean T

[PATCH] neigh: always use hash_mask under tbl lock

2006-10-02 Thread Julian Anastasov
Make sure hash_mask is protected with tbl->lock in all cases just like the hash_buckets. Signed-off-by: Julian Anastasov <[EMAIL PROTECTED]> --- I just noticed this in sources. Let me know if such change is valid and desired for 2.4 or stable tree. Compiles on 2.6.18 and 2.6.18-gi

Re: [PATCH 1/2] remove Momentum Jaguar ATX network driver support

2006-10-02 Thread Ralf Baechle
On Mon, Oct 02, 2006 at 11:33:44PM +0900, Yoichi Yuasa wrote: > This patch has removed Momentum / PMC-Sierra Jaguar ATX network driver > support. > It is listed in feature-removal-schedule.txt . NAK. I won't remove the Momentum / Ocelot support for now. Ralf - To unsubscribe from this list:

Re: Network problem with 2.6.18-mm1 ?

2006-10-02 Thread Badari Pulavarty
On Fri, 2006-09-29 at 17:30 -0600, Eric W. Biederman wrote: > > So it looks like the kernel moved the ioapics. > > The following patch in 2.6.18-mm1 is known to have that effect. > x86_64-mm-insert-ioapics-and-local-apic-into-resource-map > > Can you please try reverting that one patch? >

Re: cubic tcp behaviour

2006-10-02 Thread Douglas Leith
Thanks for posting your measurements on the web Injong. Without getting into the merits or otherwise of the coefficient of variation as a measure of anything users might care about, the individual time history plots of throughput and cwnd look interesting. I wonder if I could flag up some cur

[PATCH v3 0/1] One more time ...

2006-10-02 Thread paul . moore
Version 3 of the NetLabel support for the secid patchset. This version takes into account comments made by Stephen Smalley. -- paul moore linux security @ hp - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at h

[ANNOUNCE] iproute2-2.6.18-061002

2006-10-02 Thread Stephen Hemminger
This is a much delayed update to the iproute2 command set. It can be downloaded from: http://developer.osdl.org/dev/iproute2/download/iproute2-2.6.18-061002.tar.gz Repository: git://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git For more info on iproute2 see: http://linux-n

[PATCH v3 1/1] NetLabel: secid reconciliation support

2006-10-02 Thread paul . moore
This patch provides the missing NetLabel support to the secid reconciliation patchset. Signed-off-by: Paul Moore <[EMAIL PROTECTED]> --- security/selinux/hooks.c| 80 ++--- security/selinux/include/objsec.h |1 security/selinux/include/selinux_

Re: [PATCH] Network Events Connector

2006-10-02 Thread David Miller
From: Samir Bellabes <[EMAIL PROTECTED]> Date: Mon, 02 Oct 2006 08:11:06 +0200 > This patch adds a connector which reports networking's events to > userspace. It's sending events when a sock has its sk_state changed to : > - LISTEN or CLOSE for DCCP and TCP > - BIND or CLOSE for UDP. > > With

Re: [PATCH v2 1/1] NetLabel: secid reconciliation support

2006-10-02 Thread Paul Moore
Stephen Smalley wrote: > On Mon, 2006-10-02 at 14:06 -0400, [EMAIL PROTECTED] wrote: > >>plain text document attachment (netlabel-secid_support) >>This patch provides the missing NetLabel support to the secid reconciliation >>patchset. >> >>Signed-off-by: Paul Moore <[EMAIL PROTECTED]> >>--- >> se

RE: [PATCH v2 1/1] NetLabel: secid reconciliation support

2006-10-02 Thread Venkat Yekkirala
> > If this selinux_netlbl_skb_sid() call can fail for any > reason other than > > a kernel bug, then this needs to goto out instead of using > BUG_ON. For > > example, if the function can fail due to temporary memory pressure > > leading to a failed allocation, then you want to simply > drop t

Re: 2.6.18-mm2 - oops in cache_alloc_refill()

2006-10-02 Thread Valdis . Kletnieks
On Mon, 02 Oct 2006 10:52:45 PDT, Jean Tourrilhes said: > On Fri, Sep 29, 2006 at 06:20:08PM -0700, Andrew Morton wrote: > > On Fri, 29 Sep 2006 20:01:54 -0400 > > > > > > % grep ioctl /tmp/foo2 | sort -u | more > > > ioctl(13, SIOCGIWESSID, 0xbfbcdb9c) = 0 > > > ioctl(13, SIOCGIWRANGE, 0xbfbc

Re: [PATCH v2 1/1] NetLabel: secid reconciliation support

2006-10-02 Thread Paul Moore
Stephen Smalley wrote: > On Mon, 2006-10-02 at 14:06 -0400, [EMAIL PROTECTED] wrote: > >>plain text document attachment (netlabel-secid_support) >>This patch provides the missing NetLabel support to the secid reconciliation >>patchset. >> >>Signed-off-by: Paul Moore <[EMAIL PROTECTED]> >>--- >> se

Re: [PATCH v2 1/1] NetLabel: secid reconciliation support

2006-10-02 Thread Stephen Smalley
On Mon, 2006-10-02 at 14:06 -0400, [EMAIL PROTECTED] wrote: > plain text document attachment (netlabel-secid_support) > This patch provides the missing NetLabel support to the secid reconciliation > patchset. > > Signed-off-by: Paul Moore <[EMAIL PROTECTED]> > --- > security/selinux/hooks.c

RE: [PATCH] Fix for IPsec leakage with SELinux enabled

2006-10-02 Thread Venkat Yekkirala
> > This is indeed the "designed" and expected (for me) behavior. > > This is a security hole. SELinux denies all access by > default, so the > default behavior of this code is to allow all traffic to bypass IPsec. > > You should not need to add a rule to 'allow' increased security. You are r

RE: [PATCH] Fix for IPsec leakage with SELinux enabled

2006-10-02 Thread James Morris
On Mon, 2 Oct 2006, Venkat Yekkirala wrote: > This is indeed the "designed" and expected (for me) behavior. This is a security hole. SELinux denies all access by default, so the default behavior of this code is to allow all traffic to bypass IPsec. You should not need to add a rule to 'allow'

[PATCH 6/8] d80211: proper rate control structures freeing

2006-10-02 Thread Jiri Benc
Add a reference counting to the rate control algorithm structure. This prevents unloading of the rate control module when there still exists a sta entry which uses that module. To achieve this some other things need to be done in this patch as well: - The new rate_control_ref structure is introdu

[PATCH 0/8] d80211: rate control modules locking and changing

2006-10-02 Thread Jiri Benc
The following patch series fixes locking issues with rate control modules and adds support for on-the-fly changing of the rate control algorithms. During the work I discovered some bugs which are not exactly related to rate controling; they are included in the series as well. All patches are also

[PATCH 3/8] d80211: rename rate_control.h to ieee80211_rate.h

2006-10-02 Thread Jiri Benc
rate_control.h is not a header for rate_control.c as the name suggests. Furthermore, we want to introduce ieee80211_rate.c which implements some things defined in rate_control.h. This patch renames rate_control.h to ieee80211_rate.h. Signed-off-by: Jiri Benc <[EMAIL PROTECTED]> --- net/d80211/

[PATCH 7/8] d80211: allow changing of the rate control algorithm

2006-10-02 Thread Jiri Benc
Allow changing of the rate control algorithm. This has some limitations: - The rate control algorithm can be set per-wiphy only. - All of network interfaces of the wiphy have to be down to change the algorithm. - All sta entries are flushed when the algorithm is succesfully changed. - The add_st

[PATCH 2/8] d80211: del sta timer on interface close

2006-10-02 Thread Jiri Benc
Delete sta timer when the corresponding network interface is brought down. Signed-off-by: Jiri Benc <[EMAIL PROTECTED]> --- net/d80211/ieee80211.c | 24 net/d80211/ieee80211_i.h |1 + net/d80211/ieee80211_iface.c | 12 +++- net/d80211/ieee80211

[PATCH 8/8] d80211: rate_control: do not use atomic allocations when not necessary

2006-10-02 Thread Jiri Benc
Allow GFP_KERNEL to be used for allocations of sta entries triggered from the user space. Signed-off-by: Jiri Benc <[EMAIL PROTECTED]> --- net/d80211/ieee80211_ioctl.c |2 +- net/d80211/ieee80211_rate.h |7 --- net/d80211/ieee80211_sta.c |4 ++-- net/d80211/rc80211_simple.c

d80211: for testing only: really stupid rate control algorithm

2006-10-02 Thread Jiri Benc
This is a rate control algorithm intended for the testing of rate modules changing. It's name is "lowest". It uses always the lowest rate available. Usage: echo -n lowest > /sys/class/ieee80211/phy0/rate_ctrl_alg --- net/d80211/Makefile |2 - net/d80211/rc80211_lowest.c | 106 +

[PATCH 4/8] d80211: proper rate_control loading

2006-10-02 Thread Jiri Benc
Fix locking issues with loading of rate_control modules. This still doesn't allow changing of the modules on the fly. Signed-off-by: Jiri Benc <[EMAIL PROTECTED]> --- net/d80211/Makefile |1 net/d80211/ieee80211.c | 108 ++- net/d80211/

[PATCH 5/8] d80211: rename rate_control.c to rc80211_simple.c

2006-10-02 Thread Jiri Benc
To support changing of the rate control modules on the fly we need well-defined names of the modules. Let it be rc80211_*. Rename the only one rate control module (rate_control.c) into rc80211_simple.c. The module alias for the default module is changed to rc80211_default. Signed-off-by: Jiri Ben

[PATCH 1/8] d80211: add missing rtnl_unlock()

2006-10-02 Thread Jiri Benc
Add forgotten rtnl_unlock() in the error path of ieee80211_register_hw. Signed-off-by: Jiri Benc <[EMAIL PROTECTED]> --- net/d80211/ieee80211.c |4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) a0ed5768c0c3b9481dda8b59f6a183e000451acf diff --git a/net/d80211/ieee80211.c b/net/d8021

[PATCH v2 1/1] NetLabel: secid reconciliation support

2006-10-02 Thread paul . moore
This patch provides the missing NetLabel support to the secid reconciliation patchset. Signed-off-by: Paul Moore <[EMAIL PROTECTED]> --- security/selinux/hooks.c| 67 +++-- security/selinux/include/objsec.h |1 security/selinux/include/selinux_netl

[PATCH v2 0/1] Respun patch to match the latest secid patchset

2006-10-02 Thread paul . moore
This patchset is against the net-2.6 tree from this morning plus the secid patches posted by Venkat yesterday night. Unfortunately the net-2.6 trees from the past few days seem to have problems booting on my test machine, so testing of this patch has been ... well ... "minimal". However, I know t

Re: 2.6.18-mm2 - oops in cache_alloc_refill()

2006-10-02 Thread Jean Tourrilhes
On Fri, Sep 29, 2006 at 06:20:08PM -0700, Andrew Morton wrote: > On Fri, 29 Sep 2006 20:01:54 -0400 > > > > % grep ioctl /tmp/foo2 | sort -u | more > > ioctl(13, SIOCGIWESSID, 0xbfbcdb9c) = 0 > > ioctl(13, SIOCGIWRANGE, 0xbfbcdbdc) = 0 > > ioctl(13, SIOCGIWRATE, 0xbfbcdbbc) = 0 > > Y

[PATCH] wext

2006-10-02 Thread chunkeey
This patch (wext-patch) is a proposal. It adds two new defines for the SIOCSIWMLME to cover all kinds MLMEs (well, except REASSOC) through a ioctl. (it would be nice to have them, so that I can post the hostapd code for the prism54 card!) I didn't update the changelog! but this should be done in

Re: [PATCH 6/6]: powerpc/cell spidernet refine locking

2006-10-02 Thread Linas Vepstas
On Fri, Sep 29, 2006 at 07:47:52PM -0700, Andrew Morton wrote: > On Fri, 29 Sep 2006 18:29:11 -0500 > [EMAIL PROTECTED] (Linas Vepstas) wrote: > > > The transmit side of the spider ethernet driver currently > > places locks around some very large chunks of code. This > > results in a fair amount o

Re: [PATCH 7/9] secid reconciliation-v04: Enforcement for SELinux

2006-10-02 Thread Paul Moore
Venkat Yekkirala wrote: >>My immediate concern is not really what selinux_xfrm_decode_session() >>returns, but how to handle it, or rather errors in general, in >>selinux_skb_flow_in(). I'm in the process of creating a patch to add >>the missing NetLabel support to the secid patches and I am >>wo

RE: [PATCH 7/9] secid reconciliation-v04: Enforcement for SELinux

2006-10-02 Thread Venkat Yekkirala
> My immediate concern is not really what selinux_xfrm_decode_session() > returns, but how to handle it, or rather errors in general, in > selinux_skb_flow_in(). I'm in the process of creating a patch to add > the missing NetLabel support to the secid patches and I am > wondering if > I should BU

Re: [PATCH 0/6]: powerpc/cell spidernet ethernet patches

2006-10-02 Thread Linas Vepstas
On Mon, Oct 02, 2006 at 06:50:39PM +0200, Arnd Bergmann wrote: > On Monday 02 October 2006 18:27, Linas Vepstas wrote: > > > > > > I'm not sure if I have missed a patch in here, but I > > > don't see anything reintroducing the 'netif_stop_queue' > > > that is missing from the transmit path. > > >

RE: [PATCH] Fix for IPsec leakage with SELinux enabled

2006-10-02 Thread Venkat Yekkirala
> On Sun, 1 Oct 2006, Venkat Yekkirala wrote: > > > > The way I was seeing the problem was when connecting via > IPsec to a > > > confined service on an SELinux box (vsftpd), which did > not have the > > > appropriate SELinux policy permissions to send packets via IPsec. > > > > > > The first

Re: [PATCH 4/6]: powerpc/cell spidernet ethtool -i version number info.

2006-10-02 Thread Linas Vepstas
On Sat, Sep 30, 2006 at 12:33:45PM +0200, Arnd Bergmann wrote: > Am Saturday 30 September 2006 01:21 schrieb Linas Vepstas: > > > >  static int __init spider_net_init(void) > >  { > > +   printk("spidernet Version %s.\n",VERSION); > > + > > This is missing a printk level and a space character.

Re: [PATCH 7/9] secid reconciliation-v04: Enforcement for SELinux

2006-10-02 Thread Paul Moore
Stephen Smalley wrote: > On Mon, 2006-10-02 at 12:12 -0400, Paul Moore wrote: > >>Venkat Yekkirala wrote: >> >>>This defines SELinux enforcement of the 2 new LSM hooks as well >>>as related changes elsewhere in the SELinux code. >>> >>>This also now keeps track of the peersid thru the establishmen

Re: [PATCH 0/6]: powerpc/cell spidernet ethernet patches

2006-10-02 Thread Arnd Bergmann
On Monday 02 October 2006 18:27, Linas Vepstas wrote: > > > > I'm not sure if I have missed a patch in here, but I > > don't see anything reintroducing the 'netif_stop_queue' > > that is missing from the transmit path. > > > > Do you have a extra patch for that? > > Unfinished.  There are severa

Please pull bcm43xx-d80211 bugfixes and new features

2006-10-02 Thread Michael Buesch
Hi John, Please pull from my tree git pull http://bu3sch.de/git/wireless-dev.git for-linville This will pull various bugfixes and feature improvements. Most noteably it will pull a bugfix for a crash introduced by an earlier patch to d80211 which changed RX status information handling. The new f

Re: [PATCH 7/9] secid reconciliation-v04: Enforcement for SELinux

2006-10-02 Thread James Morris
On Mon, 2 Oct 2006, Stephen Smalley wrote: > It appears that selinux_xfrm_decode_session() can only legitimately > return an error if the last argument (ckall) is non-zero. > security_skb_classify_flow() was doing the same thing prior to this > patch series. It would be clearer if there were two

Re: [PATCH 2/9] secid reconciliation-v04: Add LSM hooks

2006-10-02 Thread Stephen Smalley
On Sun, 2006-10-01 at 16:26 -0500, Venkat Yekkirala wrote: > Add skb_policy_check and skb_netfilter_check hooks to LSM to enable > reconciliation of the various security identifiers as well as enforce > flow control on inbound (PREROUTING/INPUT) and outbound > (OUTPUT/FORWARD/POSTROUTING) > traffi

Re: [PATCH] Fix for IPsec leakage with SELinux enabled - V.02

2006-10-02 Thread James Morris
On Mon, 2 Oct 2006, Evgeniy Polyakov wrote: > > Can you look in /var/log/audit/audit.log ? (especially grep for > > 'association' ) > > Indeed. > > type=AVC msg=audit(1159804556.391:21): avc: denied { polmatch } for > pid=2213 comm="racoon" scontext=root:system_r:unconfined_t:s0-s0:c0.c255 >

Re: [PATCH 7/9] secid reconciliation-v04: Enforcement for SELinux

2006-10-02 Thread Stephen Smalley
On Mon, 2006-10-02 at 12:12 -0400, Paul Moore wrote: > Venkat Yekkirala wrote: > > This defines SELinux enforcement of the 2 new LSM hooks as well > > as related changes elsewhere in the SELinux code. > > > > This also now keeps track of the peersid thru the establishment > > of a connection on th

Re: [PATCH] Fix for IPsec leakage with SELinux enabled - V.02

2006-10-02 Thread Evgeniy Polyakov
On Mon, Oct 02, 2006 at 12:13:45PM -0400, James Morris ([EMAIL PROTECTED]) wrote: > On Mon, 2 Oct 2006, Evgeniy Polyakov wrote: > > > On Mon, Oct 02, 2006 at 10:27:13AM -0400, James Morris ([EMAIL PROTECTED]) > > wrote: > > > Updated version of the patch, which return directly after a flow cache

Re: [PATCH 0/6]: powerpc/cell spidernet ethernet patches

2006-10-02 Thread Linas Vepstas
On Sat, Sep 30, 2006 at 12:40:00PM +0200, Arnd Bergmann wrote: > Am Saturday 30 September 2006 01:05 schrieb Linas Vepstas: > > > > Although these patches improve things, I am not > > satisfied with how this driver behaves, and so > > plan to do additional work next week. > > > > I'm not sure if I

Re: [PATCH] Fix for IPsec leakage with SELinux enabled - V.02

2006-10-02 Thread James Morris
On Mon, 2 Oct 2006, Evgeniy Polyakov wrote: > On Mon, Oct 02, 2006 at 10:27:13AM -0400, James Morris ([EMAIL PROTECTED]) > wrote: > > Updated version of the patch, which return directly after a flow cache > > lookup error in xfrm_lookup rather than returing via the cleanup path > > (which was c

Re: [PATCH 7/9] secid reconciliation-v04: Enforcement for SELinux

2006-10-02 Thread Paul Moore
Venkat Yekkirala wrote: > This defines SELinux enforcement of the 2 new LSM hooks as well > as related changes elsewhere in the SELinux code. > > This also now keeps track of the peersid thru the establishment > of a connection on the server (tracking peersid on the client > is covered later in th

Re: [PATCH] Fix for IPsec leakage with SELinux enabled - V.02

2006-10-02 Thread Evgeniy Polyakov
On Mon, Oct 02, 2006 at 10:27:13AM -0400, James Morris ([EMAIL PROTECTED]) wrote: > Updated version of the patch, which return directly after a flow cache > lookup error in xfrm_lookup rather than returing via the cleanup path > (which was causing a spurious dst_release). > > This works for me,

Re: [PATCH] Introduce BROKEN_ON_64BIT facility

2006-10-02 Thread Alan Cox
> (whitespace damaged; more for comment than for application). > > > -if ((u32)skb->data & 3) { > > +if ((unsigned long)skb->data & 3) { > > I suppose it quietens a compiler warning. Doesn't actually fix a bug > though. Right but it does no harm casting it to either so its worth

Re: [PATCH] Introduce BROKEN_ON_64BIT facility

2006-10-02 Thread Matthew Wilcox
On Mon, Oct 02, 2006 at 04:12:35PM +0100, Alan Cox wrote: > @@ -1423,14 +1418,15 @@ > printk(KERN_ERR DEV_LABEL "can't allocate DLEs\n"); > goto err_out; > } > - iadev->rx_dle_q.start = (struct dle*)dle_addr; > + iadev->rx_dle_q.start = (struct dle *)dle_

Re: [PATCH] Introduce BROKEN_ON_64BIT facility

2006-10-02 Thread Alan Cox
Ar Llu, 2006-10-02 am 09:52 -0400, ysgrifennodd chas williams - CONTRACTOR: > some of the drivers in atm are already marked with !64BIT and some > need to be marked. this might be more complete for drivers/atm/Kconfig: This should fix Iphase for one. Some of the others look a lot harder however

Re: rewriting skb->truesize... good or bad idea

2006-10-02 Thread Vlad Yasevich
Hi David Thanks for the answer. David Miller wrote: > From: Vlad Yasevich <[EMAIL PROTECTED]> > Date: Fri, 29 Sep 2006 14:16:57 -0400 > >> I've attached the patch, in case people want to look at the code. >> >> However, we question if this is a good idea or if this is going to break >> things...

[PATCH 1/2] remove Momentum Jaguar ATX network driver support

2006-10-02 Thread Yoichi Yuasa
This patch has removed Momentum / PMC-Sierra Jaguar ATX network driver support. It is listed in feature-removal-schedule.txt . Yoichi Signed-off-by: Yoichi Yuasa <[EMAIL PROTECTED]> diff -pruN -X generic/Documentation/dontdiff generic-orig/drivers/net/Kconfig generic/drivers/net/Kconfig --- gen

[PATCH 2/2] remove Momentum Ocelot 3 andOcelot C network driver support

2006-10-02 Thread Yoichi Yuasa
This patch has removed Momentum Ocelot 3 and Ocelot C network driver support. It is listed in feature-removal-schedule.txt . Yoichi Signed-off-by: Yoichi Yuasa <[EMAIL PROTECTED]> diff -pruN -X generic/Documentation/dontdiff generic-orig/drivers/net/Kconfig generic/drivers/net/Kconfig --- gener

[PATCH] Fix for IPsec leakage with SELinux enabled - V.02

2006-10-02 Thread James Morris
Updated version of the patch, which return directly after a flow cache lookup error in xfrm_lookup rather than returing via the cleanup path (which was causing a spurious dst_release). This works for me, although I never saw the oops with the old patch. Evgeniy, let me know if this fixes the oo

Re: [PATCH] Introduce BROKEN_ON_64BIT facility

2006-10-02 Thread Markus Lidel
Hello, Jeff Garzik wrote: Andi Kleen wrote: Jeff Garzik <[EMAIL PROTECTED]> writes: Add a broken-on-64bit option, similar to the existing broken-on-smp config option. This is just the first pass, marking the obvious candidates. When I had this problem in the past I just used && !64BIT. How i

Re: [PATCH] Fix for IPsec leakage with SELinux enabled

2006-10-02 Thread James Morris
On Mon, 2 Oct 2006, Evgeniy Polyakov wrote: > Probably reference counter is inside freed object... I think I know what it is (xfrm_lookup needs to just return on flow cache lookup failure, not goto error and free the dst). Patch forthcoming. - James -- James Morris <[EMAIL PROTECTED]> - To

Re: [PATCH] Introduce BROKEN_ON_64BIT facility

2006-10-02 Thread Alan Cox
Ar Llu, 2006-10-02 am 00:55 -0400, ysgrifennodd Jeff Garzik: > Add a broken-on-64bit option, similar to the existing broken-on-smp > config option. This is just the first pass, marking the obvious > candidates. NAK. This contains lots of stuff whcih isn't broken in the first place. (Eg Megaraid

Re: [PATCH] genetlink custom attribute type

2006-10-02 Thread Johannes Berg
On Mon, 2006-10-02 at 15:49 +0200, Thomas Graf wrote: > That's not a bad idea, although it seems cleaner to just allow defining > a callback function which gets called foreach unknown attribute. Hm, that'd work too, but it'd force me to leave these 'unknown attributes' at the end of the attribute

Re: [PATCH] Introduce BROKEN_ON_64BIT facility

2006-10-02 Thread chas williams - CONTRACTOR
In message <[EMAIL PROTECTED]>,Jeff Garzik writes: >Several driver have been marked as dependent on CONFIG_32BIT in the >past, when they should really be dependent on this new >CONFIG_BROKEN_ON_64BIT option, because the 32BIT marker was due to bugs >rather than fundamentals. some of the drivers in

Re: [PATCH] Revert [NET_SCHED]: HTB: fix incorrect use of RB_EMPTY_NODE

2006-10-02 Thread Ismail Donmez
02 Eki 2006 Pts 13:24 tarihinde, Jarek Poplawski şunları yazmıştı: > On 30-09-2006 21:23, Ismail Donmez wrote: > > Hi, > > > > With commit 10fd48f2376db52f08bf0420d2c4f580e39269e1 [1] , RB_EMPTY_NODE > > changed behaviour so it returns false when the node is empty as expected. > > ... > > > - i

Re: [PATCH] genetlink custom attribute type

2006-10-02 Thread Thomas Graf
* Johannes Berg <[EMAIL PROTECTED]> 2006-09-27 14:18 > On Tue, 2006-09-26 at 11:44 +0200, Thomas Graf wrote: > > > Thinking it over I'm still not completely happy with this. A > > small subset of all the validation tasks is simply too complex > > to be put into the policy. The validation of your t

Re: [PATCH] Fix for IPsec leakage with SELinux enabled

2006-10-02 Thread Evgeniy Polyakov
On Mon, Oct 02, 2006 at 09:31:36AM -0400, James Morris ([EMAIL PROTECTED]) wrote: > What kind of traffic was running over the system? What is the IPsec and > SELinux configuration? I had login through ssh, started racoon and setup keys. SElinu is configured by default in FC5 system with enforci

Re: [PATCH] Fix for IPsec leakage with SELinux enabled

2006-10-02 Thread James Morris
On Mon, 2 Oct 2006, Evgeniy Polyakov wrote: > > Evgeniy, please let me know if this fixes your problem. > > With that patch applied I got kernel panic after some time. > Unfortunately I have not installed serial console, so the most > interesting bits of the stack dump are not visible. > Here is

Re: [PATCH] Network Events Connector

2006-10-02 Thread Evgeniy Polyakov
On Mon, Oct 02, 2006 at 02:57:55PM +0200, Samir Bellabes ([EMAIL PROTECTED]) wrote: > Evgeniy Polyakov <[EMAIL PROTECTED]> writes: > > > On Mon, Oct 02, 2006 at 08:11:06AM +0200, Samir Bellabes ([EMAIL > > PROTECTED]) wrote: > >> > >> This patch adds a connector which reports networking's event

Re: [PATCH] Network Events Connector

2006-10-02 Thread Samir Bellabes
Evgeniy Polyakov <[EMAIL PROTECTED]> writes: > On Mon, Oct 02, 2006 at 08:11:06AM +0200, Samir Bellabes ([EMAIL PROTECTED]) > wrote: >> >> This patch adds a connector which reports networking's events to >> userspace. It's sending events when a sock has its sk_state changed to : >> - LISTEN or

Re: [PATCH] Revert [NET_SCHED]: HTB: fix incorrect use of RB_EMPTY_NODE

2006-10-02 Thread Jarek Poplawski
On Mon, Oct 02, 2006 at 01:15:55PM +0200, Jarek Poplawski wrote: ... > instead of: > > + if (RB_EMPTY_NODE(rb)) should be: + if (RB_EMPTY_NODE(node)) Jarek P. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at

Re: [PATCH] Fix for IPsec leakage with SELinux enabled

2006-10-02 Thread Evgeniy Polyakov
On Sun, Oct 01, 2006 at 02:27:13AM -0400, James Morris ([EMAIL PROTECTED]) wrote: > Please review this patch carefully. It addresses a couple of issues. > > When a security module is loaded (in this case, SELinux), the > security_xfrm_policy_lookup() hook can return an access denied permission

[PATCH] fix bcm43xx-d80211 for inode diet

2006-10-02 Thread Johannes Berg
This patch propagates the inode diet changes to bcm43xx-d80211. Signed-off-by: Johannes Berg <[EMAIL PROTECTED]> --- This patch is required for compiling bcm43xx-d80211 after pulling the inode diet changes that went into Linus's tree into wireless-dev, since bcm43xx-d80211 is not in mainline it wa

Re: [PATCH] Revert [NET_SCHED]: HTB: fix incorrect use of RB_EMPTY_NODE

2006-10-02 Thread Jarek Poplawski
On Mon, Oct 02, 2006 at 12:24:47PM +0200, Jarek Poplawski wrote: > On 30-09-2006 21:23, Ismail Donmez wrote: > > Hi, > > > > With commit 10fd48f2376db52f08bf0420d2c4f580e39269e1 [1] , RB_EMPTY_NODE > > changed behaviour so it returns false when the node is empty as expected. > ... > > - if (!

Re: [PATCH 5/5] Solve host error problem in low performance embedded system when continune down and up.

2006-10-02 Thread Frederik Deweerdt
On Mon, Oct 02, 2006 at 02:26:36PM -0400, Jesse Huang wrote: > From: Jesse Huang <[EMAIL PROTECTED]> > > Change Logs: > Solve host error problem in low performance embedded system when continune > down and up. > > Signed-off-by: Jesse Huang <[EMAIL PROTECTED]> > --- > > drivers/net/sundance.c

Re: [PATCH] Revert [NET_SCHED]: HTB: fix incorrect use of RB_EMPTY_NODE

2006-10-02 Thread Jarek Poplawski
On 30-09-2006 21:23, Ismail Donmez wrote: > Hi, > > With commit 10fd48f2376db52f08bf0420d2c4f580e39269e1 [1] , RB_EMPTY_NODE > changed behaviour so it returns false when the node is empty as expected. ... > - if (!RB_EMPTY_NODE(rb)) { > + if (RB_EMPTY_NODE(rb)) { Maybe you have some ki

Re: [PATCH 5/5] Solve host error problem in low performance embedded system when continune down and up.

2006-10-02 Thread Jesse Huang
In some low performance embedded CPU, if continued to ifconfig up and down driver. It will cause host error. Driver need to make sure all counter is clear to zero, and hardware actually stop. - Original Message - From: "Andrew Morton" <[EMAIL PROTECTED]> To: "Jesse Huang" <[EMAIL PROTECTE

Re: [PATCH 2/5] Fix TX Pause bug (reset_tx, intr_handler)

2006-10-02 Thread Jesse Huang
When TxUnderrun happen, driver will re-enable tx. But during this enable process, TxUnderrun maybe happen again. So driver need to make sure Tx was actually enabled. - Original Message - From: "Andrew Morton" <[EMAIL PROTECTED]> To: "Jesse Huang" <[EMAIL PROTECTED]> Cc: ; ; <[EMAIL PROTEC

Re: [PATCH] Introduce BROKEN_ON_64BIT facility

2006-10-02 Thread Jeff Garzik
Andi Kleen wrote: Jeff Garzik <[EMAIL PROTECTED]> writes: Add a broken-on-64bit option, similar to the existing broken-on-smp config option. This is just the first pass, marking the obvious candidates. When I had this problem in the past I just used && !64BIT. How is this new option differen

Re: [PATCH] Introduce BROKEN_ON_64BIT facility

2006-10-02 Thread Andi Kleen
Jeff Garzik <[EMAIL PROTECTED]> writes: > Add a broken-on-64bit option, similar to the existing broken-on-smp > config option. This is just the first pass, marking the obvious > candidates. When I had this problem in the past I just used && !64BIT. How is this new option different? > config ISD

Re: [RFC] cfg80211 and nl80211

2006-10-02 Thread Johannes Berg
James, Good points. Just a few comments. > The EEPROM contents typically represent the configuration and operating > parameters which have been tested and certified to be operational. > > These would represent the only settings which a user can operate with > and still be covered by existing cer

Re: [PATCH] Network Events Connector

2006-10-02 Thread Evgeniy Polyakov
On Mon, Oct 02, 2006 at 08:11:06AM +0200, Samir Bellabes ([EMAIL PROTECTED]) wrote: > > This patch adds a connector which reports networking's events to > userspace. It's sending events when a sock has its sk_state changed to : > - LISTEN or CLOSE for DCCP and TCP > - BIND or CLOSE for UDP. >

Re: [PATCH 1/5] remove TxStartThresh and RxEarlyThresh

2006-10-02 Thread Jesse Huang
Sorry, I had typed wrong word. It is because patent issue. Thnaks. - Original Message - From: "Roland Dreier" <[EMAIL PROTECTED]> To: "Andrew Morton" <[EMAIL PROTECTED]> Cc: "Jesse Huang" <[EMAIL PROTECTED]>; ; ; <[EMAIL PROTECTED]> Sent: Monday, October 02, 2006 3:00 PM Subject: Re: [PA

Re: [PATCH 1/5] remove TxStartThresh and RxEarlyThresh

2006-10-02 Thread Roland Dreier
> > For pattern issue need to remove TxStartThresh and RxEarlyThresh. > Please describe this issue more completely. > > What are the implications of simply removing this feature? Presumably that > code was there for a reason.. Actually I think this patch needs to be handled delicately -- b