1) kvaser CAN driver has fixed limits of some of it's table, validate that
we won't exceed those limits at probe time. Fix from Olivier Sobrie.
2) Fix rtl8192ce disabling interrupts for too long, from Olivier Langlois.
3) Fix botched shift in ath5k driver, from Dan Carpenter.
4) Fix
1) kvaser CAN driver has fixed limits of some of it's table, validate that
we won't exceed those limits at probe time. Fix from Olivier Sobrie.
2) Fix rtl8192ce disabling interrupts for too long, from Olivier Langlois.
3) Fix botched shift in ath5k driver, from Dan Carpenter.
4) Fix
1) Fix flexcan build on big endian, from Arnd Bergmann.
2) Correctly attach cpsw to GPIO bitbang MDIO drive, from Stefan Roese.
3) udp_add_offload has to use GFP_ATOMIC since it can be invoked from
non-sleepable contexts. From Or Gerlitz.
4) vxlan_gro_receive() does not iterate over all
1) Fix flexcan build on big endian, from Arnd Bergmann.
2) Correctly attach cpsw to GPIO bitbang MDIO drive, from Stefan Roese.
3) udp_add_offload has to use GFP_ATOMIC since it can be invoked from
non-sleepable contexts. From Or Gerlitz.
4) vxlan_gro_receive() does not iterate over all
Several fixups, of note:
1) Fix unlock of not held spinlock in RXRPC code, from Alexey
Khoroshilov.
2) Call pci_disable_device() from the correct shutdown path in
bnx2x driver, from Yuval Mintz.
3) Fix qeth build on s390 for some configurations, from Eugene
Crosser.
4) Cure locking
Several fixups, of note:
1) Fix unlock of not held spinlock in RXRPC code, from Alexey
Khoroshilov.
2) Call pci_disable_device() from the correct shutdown path in
bnx2x driver, from Yuval Mintz.
3) Fix qeth build on s390 for some configurations, from Eugene
Crosser.
4) Cure locking
1) The value choosen for the new SO_MAX_PACING_RATE socket option on
parisc was very poorly choosen, let's fix it while we still can.
From Eric Dumazet.
2) Our generic reciprocal divide was found to handle some edge cases
incorrectly, part of this is encoded into the BPF as deep as the
1) The value choosen for the new SO_MAX_PACING_RATE socket option on
parisc was very poorly choosen, let's fix it while we still can.
From Eric Dumazet.
2) Our generic reciprocal divide was found to handle some edge cases
incorrectly, part of this is encoded into the BPF as deep as the
Famouse last words: "final pull request" :-)
I'm sending this because Jason Wang's fixes are pretty important.
1) Add missing per-cpu stats initialization to ip6_vti. Otherwise
lockdep spits out a call trace. From Li RongQing.
2) Fix NULL oops in wireless hwsim, from Javier Lopez.
3)
Famouse last words: final pull request :-)
I'm sending this because Jason Wang's fixes are pretty important.
1) Add missing per-cpu stats initialization to ip6_vti. Otherwise
lockdep spits out a call trace. From Li RongQing.
2) Fix NULL oops in wireless hwsim, from Javier Lopez.
3) TIPC
I'm hoping this is the very last batch of networking fixes for
3.13, here goes nothing:
1) Fix crashes in VLAN's header_ops passthru.
2) Bridge multicast code needs to use BH spinlocks to prevent deadlocks
with timers. From Curt Brune.
3) ipv6 tunnels lack proper synchornization when
I'm hoping this is the very last batch of networking fixes for
3.13, here goes nothing:
1) Fix crashes in VLAN's header_ops passthru.
2) Bridge multicast code needs to use BH spinlocks to prevent deadlocks
with timers. From Curt Brune.
3) ipv6 tunnels lack proper synchornization when
Some holiday bug fixes for 3.13... There is still one bug I'd like to get fixed
before 3.13-final.
The vlan code erroneously assignes the header ops of the underlying real device
to the VLAN device above it when the real device can hardware offload VLAN
handling. That's completely bogus because
Some holiday bug fixes for 3.13... There is still one bug I'd like to get fixed
before 3.13-final.
The vlan code erroneously assignes the header ops of the underlying real device
to the VLAN device above it when the real device can hardware offload VLAN
handling. That's completely bogus because
A quick batch of fixes, including the annoying bad lock stack
problem introduced by udp_sk_rx_dst_set() locking change:
1) Use xchg() instead of sk_dst_lock() in udp_sk_rx_dst_set(), from
Eric Dumazet.
2) qlcnic bug fixes from Himanshu Madhani and Manish Chopra.
3) Update IPSEC MAINTAINERS
A quick batch of fixes, including the annoying bad lock stack
problem introduced by udp_sk_rx_dst_set() locking change:
1) Use xchg() instead of sk_dst_lock() in udp_sk_rx_dst_set(), from
Eric Dumazet.
2) qlcnic bug fixes from Himanshu Madhani and Manish Chopra.
3) Update IPSEC MAINTAINERS
1) Revert CHECKSUM_COMPLETE optimization in pskb_trim_rcsum(), I can't figure
out why it breaks things.
2) Fix comparison in netfilter ipset's hash_netnet4_data_equal(), it was
basically doing "x == x", from Dave Jones.
3) Freescale FEC driver was DMA mapping the wrong number of bytes,
1) Revert CHECKSUM_COMPLETE optimization in pskb_trim_rcsum(), I can't figure
out why it breaks things.
2) Fix comparison in netfilter ipset's hash_netnet4_data_equal(), it was
basically doing x == x, from Dave Jones.
3) Freescale FEC driver was DMA mapping the wrong number of bytes, from
Here is a pile of bug fixes that accumulated while I was in Europe.
1) In fixing kernel leaks to userspace during copying of socket
addresses, we broke a case that used to work, namely the user
providing a buffer larger than the in-kernel generic socket address
structure. This broke
Here is a pile of bug fixes that accumulated while I was in Europe.
1) In fixing kernel leaks to userspace during copying of socket
addresses, we broke a case that used to work, namely the user
providing a buffer larger than the in-kernel generic socket address
structure. This broke
I'm sending a pull request of these lingering bug fixes for networking
before the normal merge window material because some of this stuff I'd
like to get to -stable ASAP.
1) cxgb3 stopped working on 32-bit machines, fix from Ben Hutchings.
2) Structures passed via netlink for netfilter logging
I'm sending a pull request of these lingering bug fixes for networking
before the normal merge window material because some of this stuff I'd
like to get to -stable ASAP.
1) cxgb3 stopped working on 32-bit machines, fix from Ben Hutchings.
2) Structures passed via netlink for netfilter logging
Sorry I let so much accumulate, I was in Buffalo and wanted a few
things to cook in my tree for a while before sending to you. Anyways,
it's a lot of little things as usual at this stage in the game.
1) Make bonding MAINTAINERS entry reflect reality, from Andy Gospodarek.
2) Fix accidental
Sorry I let so much accumulate, I was in Buffalo and wanted a few
things to cook in my tree for a while before sending to you. Anyways,
it's a lot of little things as usual at this stage in the game.
1) Make bonding MAINTAINERS entry reflect reality, from Andy Gospodarek.
2) Fix accidental
1) Multiply in netfilter IPVS can overflow when calculating destination
weight. From Simon Kirby.
2) Use after free fixes in IPVS from Julian Anastasov.
3) SFC driver bug fixes from Daniel Pieczko.
4) Memory leak in pcan_usb_core failure paths, from Alexey Khoroshilov.
5) Locking and
1) Multiply in netfilter IPVS can overflow when calculating destination
weight. From Simon Kirby.
2) Use after free fixes in IPVS from Julian Anastasov.
3) SFC driver bug fixes from Daniel Pieczko.
4) Memory leak in pcan_usb_core failure paths, from Alexey Khoroshilov.
5) Locking and
1) If the local_df boolean is set on an SKB we have to allocate a
unique ID even if IP_DF is set in the ipv4 headers, from Ansis
Atteka.
2) Some fixups for the new chipset support that went into the sfc
driver, from Ben Hutchings.
3) Because SCTP bypasses a good chunk of, and actually
1) If the local_df boolean is set on an SKB we have to allocate a
unique ID even if IP_DF is set in the ipv4 headers, from Ansis
Atteka.
2) Some fixups for the new chipset support that went into the sfc
driver, from Ben Hutchings.
3) Because SCTP bypasses a good chunk of, and actually
1) Brown paper bag fix in HTB scheduler, class options set incorrectly due
to a typoe. Fix from Vimalkumar.
2) It's possible for the ipv6 FIB garbage collector to run before all
the necessary datastructure are setup during init, defer the notifier
registry to avoid this problem. Fix
1) Brown paper bag fix in HTB scheduler, class options set incorrectly due
to a typoe. Fix from Vimalkumar.
2) It's possible for the ipv6 FIB garbage collector to run before all
the necessary datastructure are setup during init, defer the notifier
registry to avoid this problem. Fix
A quick set of fixes, some to deal with fallout from yesterday's
net-next merge.
1) Fix compilation of bnx2x driver with CONFIG_BNX2X_SRIOV disabled, from
Dmitry Kravkov.
2) Fix a bnx2x regression caused by one of Dave Jones's mistaken braces
changes, from Eilon Greenstein.
3) Add some
A quick set of fixes, some to deal with fallout from yesterday's
net-next merge.
1) Fix compilation of bnx2x driver with CONFIG_BNX2X_SRIOV disabled, from
Dmitry Kravkov.
2) Fix a bnx2x regression caused by one of Dave Jones's mistaken braces
changes, from Eilon Greenstein.
3) Add some
1) There was a simplification in the ipv6 ndisc packet sending
attempted here, which avoided using memory accounting on the
per-netns ndisc socket for sending NDISC packets. It did fix some
important issues, but it causes regressions so it gets reverted
here too. Specifically, the
1) There was a simplification in the ipv6 ndisc packet sending
attempted here, which avoided using memory accounting on the
per-netns ndisc socket for sending NDISC packets. It did fix some
important issues, but it causes regressions so it gets reverted
here too. Specifically, the
1) Revert Johannes Berg's genetlink locking fix, because it causes
regressions.
Johannes and Pravin Shelar are working on fixing things properly.
2) Do not drop ipv6 ICMP messages without a redirected
header option, they are legal. From Duan Jiong.
3) Missing error return
1) Revert Johannes Berg's genetlink locking fix, because it causes
regressions.
Johannes and Pravin Shelar are working on fixing things properly.
2) Do not drop ipv6 ICMP messages without a redirected
header option, they are legal. From Duan Jiong.
3) Missing error return
1) Fix SKB leak in 8139cp, from Dave Jones.
2) Fix use of *_PAGES interfaces with mlx5 firmware, from
Moshe Lazar.
3) RCU conversion of macvtap introduced two races, fixes by
Eric Dumazet.
4) Synchronize statistic flows in bnx2x driver to prevent
corruption, from Dmitry Kravkov.
5)
1) Fix SKB leak in 8139cp, from Dave Jones.
2) Fix use of *_PAGES interfaces with mlx5 firmware, from
Moshe Lazar.
3) RCU conversion of macvtap introduced two races, fixes by
Eric Dumazet.
4) Synchronize statistic flows in bnx2x driver to prevent
corruption, from Dmitry Kravkov.
5)
1) Don't ignore user initiated wireless regulatory settings on cards
with custom regulatory domains, from Arik Nemtsov.
2) Fix length check of bluetooth information responses, from Jaganath
Kanakkassery.
3) Fix misuse of PTR_ERR in btusb, from Adam Lee.
4) Handle rfkill properly while
1) Don't ignore user initiated wireless regulatory settings on cards
with custom regulatory domains, from Arik Nemtsov.
2) Fix length check of bluetooth information responses, from Jaganath
Kanakkassery.
3) Fix misuse of PTR_ERR in btusb, from Adam Lee.
4) Handle rfkill properly while
1) Fix association failures not triggering a connect-failure event in
cfg80211, from Johannes Berg.
2) Eliminate a potential NULL deref with older iptables tools when
configuring xt_socket rules, from Eric Dumazet.
3) Missing RTNL locking in wireless regulatory code, from Johannes
1) Fix association failures not triggering a connect-failure event in
cfg80211, from Johannes Berg.
2) Eliminate a potential NULL deref with older iptables tools when
configuring xt_socket rules, from Eric Dumazet.
3) Missing RTNL locking in wireless regulatory code, from Johannes
A couple interesting SKB fragment handling fixes, please the usual
small bits here and there:
1) Fix 64-bit divide build failure on 32-bit platforms in mlx5, from
Tim Gardner.
2) Get rid of a stupid reimplementation on "%*phC" in our sysfs MAC
address printing helper.
3) Fix NETIF_F_SG
A couple interesting SKB fragment handling fixes, please the usual
small bits here and there:
1) Fix 64-bit divide build failure on 32-bit platforms in mlx5, from
Tim Gardner.
2) Get rid of a stupid reimplementation on %*phC in our sysfs MAC
address printing helper.
3) Fix NETIF_F_SG
Just a bunch of small fixes and tidy ups:
1) Finish the "busy_poll" renames, from Eliezer Tamir.
2) Fix RCU stalls in IFB driver, from Ding Tianhong.
3) Linearize buffers properly in tun/macvtap zerocopy code.
4) Don't crash on rmmod in vxlan, from Pravin B Shelar.
5) Spinlock used before
Just a bunch of small fixes and tidy ups:
1) Finish the busy_poll renames, from Eliezer Tamir.
2) Fix RCU stalls in IFB driver, from Ding Tianhong.
3) Linearize buffers properly in tun/macvtap zerocopy code.
4) Don't crash on rmmod in vxlan, from Pravin B Shelar.
5) Spinlock used before init
From: Markus Trippelsdorf
Date: Wed, 10 Jul 2013 14:25:23 +0200
> On 2013.07.09 at 14:53 -0700, David Miller wrote:
>>
>> Alexey Brodkin (2):
>> ethernet/arc/arc_emac - Add new driver
>> arc_emac: fix compile-time errors & warnings on PPC64
>
> This driver defaults to y for no
On 07/10/2013 04:43 PM, Josh Boyer wrote:
> On Wed, Jul 10, 2013 at 8:25 AM, Markus Trippelsdorf
> wrote:
>> +config NET_VENDOR_ARC
>> + bool "ARC devices"
>> + default y
>
> That's the option to enable the ARC vendor, not the driver. The
> driver config option is ARC_EMAC. All of
On 2013.07.10 at 08:43 -0400, Josh Boyer wrote:
> On Wed, Jul 10, 2013 at 8:25 AM, Markus Trippelsdorf
> wrote:
> > On 2013.07.09 at 14:53 -0700, David Miller wrote:
> >>
> >> Alexey Brodkin (2):
> >> ethernet/arc/arc_emac - Add new driver
> >> arc_emac: fix compile-time errors &
On Wed, Jul 10, 2013 at 8:25 AM, Markus Trippelsdorf
wrote:
> On 2013.07.09 at 14:53 -0700, David Miller wrote:
>>
>> Alexey Brodkin (2):
>> ethernet/arc/arc_emac - Add new driver
>> arc_emac: fix compile-time errors & warnings on PPC64
>
> This driver defaults to y for no reason:
>
>
On 2013.07.09 at 14:53 -0700, David Miller wrote:
>
> Alexey Brodkin (2):
> ethernet/arc/arc_emac - Add new driver
> arc_emac: fix compile-time errors & warnings on PPC64
This driver defaults to y for no reason:
+config NET_VENDOR_ARC
+ bool "ARC devices"
+ default y
--
On 2013.07.09 at 14:53 -0700, David Miller wrote:
Alexey Brodkin (2):
ethernet/arc/arc_emac - Add new driver
arc_emac: fix compile-time errors warnings on PPC64
This driver defaults to y for no reason:
+config NET_VENDOR_ARC
+ bool ARC devices
+ default y
--
On Wed, Jul 10, 2013 at 8:25 AM, Markus Trippelsdorf
mar...@trippelsdorf.de wrote:
On 2013.07.09 at 14:53 -0700, David Miller wrote:
Alexey Brodkin (2):
ethernet/arc/arc_emac - Add new driver
arc_emac: fix compile-time errors warnings on PPC64
This driver defaults to y for no
On 2013.07.10 at 08:43 -0400, Josh Boyer wrote:
On Wed, Jul 10, 2013 at 8:25 AM, Markus Trippelsdorf
mar...@trippelsdorf.de wrote:
On 2013.07.09 at 14:53 -0700, David Miller wrote:
Alexey Brodkin (2):
ethernet/arc/arc_emac - Add new driver
arc_emac: fix compile-time errors
On 07/10/2013 04:43 PM, Josh Boyer wrote:
On Wed, Jul 10, 2013 at 8:25 AM, Markus Trippelsdorf
mar...@trippelsdorf.de wrote:
+config NET_VENDOR_ARC
+ bool ARC devices
+ default y
That's the option to enable the ARC vendor, not the driver. The
driver config option is ARC_EMAC.
From: Markus Trippelsdorf mar...@trippelsdorf.de
Date: Wed, 10 Jul 2013 14:25:23 +0200
On 2013.07.09 at 14:53 -0700, David Miller wrote:
Alexey Brodkin (2):
ethernet/arc/arc_emac - Add new driver
arc_emac: fix compile-time errors warnings on PPC64
This driver defaults to y
From: Linus Torvalds
Date: Tue, 9 Jul 2013 19:50:41 -0700
> Now, I'm all for making descriptive merge commit messages, including
> improving on the summary line. So by all means write those nice merge
> messages with explanations. I think something like
>
> dc3d807d6fd9 Merge "openvswitch:
On Tue, Jul 9, 2013 at 2:53 PM, David Miller wrote:
>
> This is a re-do of the net-next pull request for the current merge
> window. The only difference from the one I made the other day is that
> this has Eliezer's interface renames and the timeout handling changes
> made based upon your
On 07/09/2013 12:32:56 PM, Linus Torvalds wrote:
On Mon, Jul 8, 2013 at 7:29 PM, Rob Landley wrote:
>
> Um, does that mean I should have cc'd you on the initmpfs patch
series
> back before the merge window opened?
So I personally don't tend to care about that kind of patch-series -
it
On Mon, Jul 8, 2013 at 7:29 PM, Rob Landley wrote:
>
> Um, does that mean I should have cc'd you on the initmpfs patch series
> back before the merge window opened?
So I personally don't tend to care about that kind of patch-series -
it doesn't really add new features to basic code unlike the
On 09/07/2013 05:48, Andrew Morton wrote:
> The feature should also be documented in the Linux manpages, please. A
> way to do that is to Cc linux-...@vger.kernel.org and Michael Kerrisk
> , and to work with Michael on developing that
> documentation.
OK
--
To unsubscribe from this list: send
On 07/09/2013 12:32:56 PM, Linus Torvalds wrote:
On Mon, Jul 8, 2013 at 7:29 PM, Rob Landley r...@landley.net wrote:
Um, does that mean I should have cc'd you on the initmpfs patch
series
back before the merge window opened?
So I personally don't tend to care about that kind of
On Tue, Jul 9, 2013 at 2:53 PM, David Miller da...@davemloft.net wrote:
This is a re-do of the net-next pull request for the current merge
window. The only difference from the one I made the other day is that
this has Eliezer's interface renames and the timeout handling changes
made based
From: Linus Torvalds torva...@linux-foundation.org
Date: Tue, 9 Jul 2013 19:50:41 -0700
Now, I'm all for making descriptive merge commit messages, including
improving on the summary line. So by all means write those nice merge
messages with explanations. I think something like
On 09/07/2013 05:48, Andrew Morton wrote:
The feature should also be documented in the Linux manpages, please. A
way to do that is to Cc linux-...@vger.kernel.org and Michael Kerrisk
mtk.manpa...@gmail.com, and to work with Michael on developing that
documentation.
OK
--
To unsubscribe from
On Mon, Jul 8, 2013 at 7:29 PM, Rob Landley r...@landley.net wrote:
Um, does that mean I should have cc'd you on the initmpfs patch series
back before the merge window opened?
So I personally don't tend to care about that kind of patch-series -
it doesn't really add new features to basic code
On Mon, 08 Jul 2013 09:38:29 +0300 Eliezer Tamir
wrote:
> On 08/07/2013 06:14, David Miller wrote:
> > From: Linus Torvalds
> > Date: Sun, 7 Jul 2013 15:33:31 -0700
> >
> >> End result: I think the code is salvageable and people who want this
> >> kind of busy-looping can have it. But I really
On 07/07/2013 04:27:54 PM, Linus Torvalds wrote:
And dammit, I'd expect the VFS people to be
cc'd on changes to the VFS layer functions. I wasn't, Al wasn't.
Um, does that mean I should have cc'd you on the initmpfs patch series
back before the merge window opened?
On 08/07/2013 06:14, David Miller wrote:
From: Linus Torvalds
Date: Sun, 7 Jul 2013 15:33:31 -0700
End result: I think the code is salvageable and people who want this
kind of busy-looping can have it. But I really don't want to merge it
as-is. I think it was badly done, I think it was badly
On 08/07/2013 06:14, David Miller wrote:
From: Linus Torvalds torva...@linux-foundation.org
Date: Sun, 7 Jul 2013 15:33:31 -0700
End result: I think the code is salvageable and people who want this
kind of busy-looping can have it. But I really don't want to merge it
as-is. I think it was
On 07/07/2013 04:27:54 PM, Linus Torvalds wrote:
And dammit, I'd expect the VFS people to be
cc'd on changes to the VFS layer functions. I wasn't, Al wasn't.
Um, does that mean I should have cc'd you on the initmpfs patch series
back before the merge window opened?
On Mon, 08 Jul 2013 09:38:29 +0300 Eliezer Tamir
eliezer.ta...@linux.intel.com wrote:
On 08/07/2013 06:14, David Miller wrote:
From: Linus Torvalds torva...@linux-foundation.org
Date: Sun, 7 Jul 2013 15:33:31 -0700
End result: I think the code is salvageable and people who want this
From: Linus Torvalds
Date: Sun, 7 Jul 2013 15:33:31 -0700
> End result: I think the code is salvageable and people who want this
> kind of busy-looping can have it. But I really don't want to merge it
> as-is. I think it was badly done, I think it was badly documented, and
> I think somebody
On Sun, Jul 7, 2013 at 2:27 PM, Linus Torvalds
wrote:
>
> Because quite frankly, the fs/select.c changes make me go: "No way in
> hell". Partly because of the idiotic and completely undescriptive
> naming, partly because of the disgisting calling convetions with
> random flags variables passed in
On Sun, Jul 7, 2013 at 1:21 PM, David Miller wrote:
>
> 5) arch/arm/mach-mxs/Kconfig
>
>Overlapping additions of select statements for SOC_IMX2.
Nope. Removals.
> 6) arch/arm/mach-mxs/mach-mxs.c
>
>In mxs_machine_init(), the of_platform_populate() call has it's final
>two arguments
On Sun, Jul 7, 2013 at 1:21 PM, David Miller da...@davemloft.net wrote:
5) arch/arm/mach-mxs/Kconfig
Overlapping additions of select statements for SOC_IMX2.
Nope. Removals.
6) arch/arm/mach-mxs/mach-mxs.c
In mxs_machine_init(), the of_platform_populate() call has it's final
two
On Sun, Jul 7, 2013 at 2:27 PM, Linus Torvalds
torva...@linux-foundation.org wrote:
Because quite frankly, the fs/select.c changes make me go: No way in
hell. Partly because of the idiotic and completely undescriptive
naming, partly because of the disgisting calling convetions with
random
From: Linus Torvalds torva...@linux-foundation.org
Date: Sun, 7 Jul 2013 15:33:31 -0700
End result: I think the code is salvageable and people who want this
kind of busy-looping can have it. But I really don't want to merge it
as-is. I think it was badly done, I think it was badly documented,
1) Found via trinity.
If you connect up an ipv6 socket to an ipv4 mapped address then an
ipv6 one, sendmsg() can croak because ip6_sk_dst_check() assumes
the route cached in the socket is an ipv6 one. In this case there
is an ipv4 route attached, so it gets stomped on.
Reported
1) Found via trinity.
If you connect up an ipv6 socket to an ipv4 mapped address then an
ipv6 one, sendmsg() can croak because ip6_sk_dst_check() assumes
the route cached in the socket is an ipv6 one. In this case there
is an ipv4 route attached, so it gets stomped on.
Reported
1) Fix RTNL locking in batman-adv, from Matthias Schiffer.
2) Don't allow non-passthrough macvlan devices to set NOPROMISC
via netlink, otherwise we can end up with corrupted promisc
counter values on the device. From Michael S. Tsirkin.
3) Fix stmmac driver build with debugging defines
1) Fix RTNL locking in batman-adv, from Matthias Schiffer.
2) Don't allow non-passthrough macvlan devices to set NOPROMISC
via netlink, otherwise we can end up with corrupted promisc
counter values on the device. From Michael S. Tsirkin.
3) Fix stmmac driver build with debugging defines
Small fixes in various spots, and the ath9k changes that should make
your Pixel's wireless behave better:
1) Fix dump iterator in nfnl_acct_dump() and ctnl_timeout_dump() to
dump all objects properly, from Pablo Neira Ayuso.
2) xt_TCPMSS must use the default MSS of 536 when no MSS TCP option
Small fixes in various spots, and the ath9k changes that should make
your Pixel's wireless behave better:
1) Fix dump iterator in nfnl_acct_dump() and ctnl_timeout_dump() to
dump all objects properly, from Pablo Neira Ayuso.
2) xt_TCPMSS must use the default MSS of 536 when no MSS TCP option
This is a quick one commit pull request to cure the
regression introduced by the MSG_CMSG_COMPAT change.
Please pull, thanks a lot!
The following changes since commit 4d3797d7e1861ac1af150a6189315786c5e1c820:
Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2013-06-05
19:19:04
This is a quick one commit pull request to cure the
regression introduced by the MSG_CMSG_COMPAT change.
Please pull, thanks a lot!
The following changes since commit 4d3797d7e1861ac1af150a6189315786c5e1c820:
Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2013-06-05
19:19:04
1) Fix timeouts with direct mode authentication in mac80211, from
Stanislaw Gruszka.
2) Aggregation sessions can deadlock in ath9k, from Felix Fietkau.
3) Netfilter's xt_addrtype doesn't work with ipv6 due to route lookups
creating undesirable cache entries, from Florian Westphal.
4) Fix
1) Fix timeouts with direct mode authentication in mac80211, from
Stanislaw Gruszka.
2) Aggregation sessions can deadlock in ath9k, from Felix Fietkau.
3) Netfilter's xt_addrtype doesn't work with ipv6 due to route lookups
creating undesirable cache entries, from Florian Westphal.
4) Fix
It's been a while since my last pull request so quite a few
fixes have piled up.
1) Fix nf_{log,queue} compilation with PROC_FS disabled, from
Pablo Neira Ayuso.
2) Fix data corruption on some tg3 chips with TSO enabled, from
Michael Chan.
3) Fix double insertion of VLAN tags in be2net
It's been a while since my last pull request so quite a few
fixes have piled up.
1) Fix nf_{log,queue} compilation with PROC_FS disabled, from
Pablo Neira Ayuso.
2) Fix data corruption on some tg3 chips with TSO enabled, from
Michael Chan.
3) Fix double insertion of VLAN tags in be2net
Hello.
On 05/14/2013 12:08 AM, David Miller wrote:
Several small bug fixes all over:
[...]
13) Fix bogus PCI resource management in 3c59x driver, from Sergei
Shtylyov.
I must note that this coming August I will be celebrating 7 (!) years
from the original posting of that patch.
Several small bug fixes all over:
1) be2net driver uses wrong payload length when submitting MAC list get
requests to the chip. From Sathya Perla.
2) Fix mwifiex memory leak on driver unload, from Amitkumar Karwar.
3) Prevent random memory access in batman-adv, from Marek Lindner.
4)
Several small bug fixes all over:
1) be2net driver uses wrong payload length when submitting MAC list get
requests to the chip. From Sathya Perla.
2) Fix mwifiex memory leak on driver unload, from Amitkumar Karwar.
3) Prevent random memory access in batman-adv, from Marek Lindner.
4)
Hello.
On 05/14/2013 12:08 AM, David Miller wrote:
Several small bug fixes all over:
[...]
13) Fix bogus PCI resource management in 3c59x driver, from Sergei
Shtylyov.
I must note that this coming August I will be celebrating 7 (!) years
from the original posting of that patch.
undation.org,
> net...@vger.kernel.org, linux-kernel@vger.kernel.org, "Dan Williams"
> , "Jiri Pirko"
>
> Sent: Saturday, May 4, 2013 1:35:35 AM
> Subject: Re: [GIT] Networking
>
> - Original Message -
> > From: "Michał Mirosław"
,
a...@linux-foundation.org,
net...@vger.kernel.org, linux-kernel@vger.kernel.org, Dan Williams
d...@redhat.com, Jiri Pirko
jpi...@redhat.com
Sent: Saturday, May 4, 2013 1:35:35 AM
Subject: Re: [GIT] Networking
- Original Message -
From: Michał Mirosław mir...@gmail.com
To: Bjørn Mork bj
1) Propagate return error values properly in irda, spider_net, sfc,
and bfin_mac. From Wei Yongjun.
2) Fix fec driver OOPS on rapid link up/down, from Frank Li.
3) FIX VF resource allocation and chip message payload length errors
in be2net driver, from Sathya Perla.
4) Fix inner
1) Propagate return error values properly in irda, spider_net, sfc,
and bfin_mac. From Wei Yongjun.
2) Fix fec driver OOPS on rapid link up/down, from Frank Li.
3) FIX VF resource allocation and chip message payload length errors
in be2net driver, from Sathya Perla.
4) Fix inner
On Mon, 2013-05-06 at 22:10 -0400, David Miller wrote:
> From: Jeff Kirsher
> Date: Mon, 06 May 2013 16:32:46 -0700
>
> > On Mon, 2013-05-06 at 19:09 -0400, David Miller wrote:
> >> From: Linus Torvalds
> >> Date: Mon, 6 May 2013 15:57:15 -0700
> >>
> >> > On Mon, May 6, 2013 at 2:05 PM, David
On Mon, 2013-05-06 at 22:10 -0400, David Miller wrote:
From: Jeff Kirsher jeffrey.t.kirs...@intel.com
Date: Mon, 06 May 2013 16:32:46 -0700
On Mon, 2013-05-06 at 19:09 -0400, David Miller wrote:
From: Linus Torvalds torva...@linux-foundation.org
Date: Mon, 6 May 2013 15:57:15 -0700
901 - 1000 of 1212 matches
Mail list logo
