02 Aug, 2011

3 commits


01 Aug, 2011

4 commits

  • commit 8efa88540635 (sch_sfq: avoid giving spurious NET_XMIT_CN signals)
    forgot to call qdisc_tree_decrease_qlen() to signal upper levels that a
    packet (from another flow) was dropped, leading to various problems.

    With help from Michal Soltys and Michal Pokrywka, who did a bisection.

    Bugzilla ref: https://bugzilla.kernel.org/show_bug.cgi?id=39372
    Debian ref: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631945

    Reported-by: Lucas Bocchi
    Reported-and-bisected-by: Michal Pokrywka
    Signed-off-by: Eric Dumazet
    CC: Michal Soltys
    Acked-by: Patrick McHardy
    Signed-off-by: David S. Miller

    Eric Dumazet
     
  • Convert array index from the loop bound to the loop index.

    A simplified version of the semantic patch that fixes this problem is as
    follows: (http://coccinelle.lip6.fr/)

    //
    @@
    expression e1,e2,ar;
    @@

    for(e1 = 0; e1 < e2; e1++) { }
    //

    Signed-off-by: Julia Lawall
    Signed-off-by: David S. Miller

    Julia Lawall
     
  • Convert array index from the loop bound to the loop index.

    A simplified version of the semantic patch that fixes this problem is as
    follows: (http://coccinelle.lip6.fr/)

    //
    @@
    expression e1,e2,ar;
    @@

    for(e1 = 0; e1 < e2; e1++) { }
    //

    Signed-off-by: Julia Lawall
    Signed-off-by: David S. Miller

    Julia Lawall
     
  • Signed-off-by: David S. Miller

    David S. Miller
     

29 Jul, 2011

7 commits


28 Jul, 2011

26 commits

  • * git://git.kernel.org/pub/scm/linux/kernel/git/davem/sparc:
    n2_crypto: Attach on Niagara-T3.
    n2rng: Attach on Niagara-T3.
    sparc: Detect and handle UltraSPARC-T3 cpu types.
    sparc: Don't do expensive hypervisor PCR write unless necessary.
    sparc: Add T3 sun4v cpu type and hypervisor group defines.
    sparc: Don't leave sparc_pmu_type NULL on sun4v.

    Linus Torvalds
     
  • * git://git.kernel.org/pub/scm/linux/kernel/git/davem/net: (32 commits)
    tg3: Remove 5719 jumbo frames and TSO blocks
    tg3: Break larger frags into 4k chunks for 5719
    tg3: Add tx BD budgeting code
    tg3: Consolidate code that calls tg3_tx_set_bd()
    tg3: Add partial fragment unmapping code
    tg3: Generalize tg3_skb_error_unmap()
    tg3: Remove short DMA check for 1st fragment
    tg3: Simplify tx bd assignments
    tg3: Reintroduce tg3_tx_ring_info
    ASIX: Use only 11 bits of header for data size
    ASIX: Simplify condition in rx_fixup()
    Fix cdc-phonet build
    bonding: reduce noise during init
    bonding: fix string comparison errors
    net: Audit drivers to identify those needing IFF_TX_SKB_SHARING cleared
    net: add IFF_SKB_TX_SHARED flag to priv_flags
    net: sock_sendmsg_nosec() is static
    forcedeth: fix vlans
    gianfar: fix bug caused by 87c288c6e9aa31720b72e2bc2d665e24e1653c3e
    gro: Only reset frag0 when skb can be pulled
    ...

    Linus Torvalds
     
  • * 'for-linus' of git://neil.brown.name/md: (75 commits)
    md/raid10: handle further errors during fix_read_error better.
    md/raid10: Handle read errors during recovery better.
    md/raid10: simplify read error handling during recovery.
    md/raid10: record bad blocks due to write errors during resync/recovery.
    md/raid10: attempt to fix read errors during resync/check
    md/raid10: Handle write errors by updating badblock log.
    md/raid10: clear bad-block record when write succeeds.
    md/raid10: avoid writing to known bad blocks on known bad drives.
    md/raid10 record bad blocks as needed during recovery.
    md/raid10: avoid reading known bad blocks during resync/recovery.
    md/raid10 - avoid reading from known bad blocks - part 3
    md/raid10: avoid reading from known bad blocks - part 2
    md/raid10: avoid reading from known bad blocks - part 1
    md/raid10: Split handle_read_error out from raid10d.
    md/raid10: simplify/reindent some loops.
    md/raid5: Clear bad blocks on successful write.
    md/raid5. Don't write to known bad block on doubtful devices.
    md/raid5: write errors should be recorded as bad blocks if possible.
    md/raid5: use bad-block log to improve handling of uncorrectable read errors.
    md/raid5: avoid reading from known bad blocks.
    ...

    Linus Torvalds
     
  • * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6:
    sound: oss: rename local change_bits to avoid powerpc bitsops.h definition
    ALSA: hda - Fix duplicated DAC assignments for Realtek
    ALSA: asihpi - off by one in asihpi_hpi_ioctl()
    ALSA: hda - Fix Oops with Realtek quirks with NULL adc_nids
    ALSA: asihpi - bug fix pa use before init.
    ALSA: hda - Add support for vref-out based mute LED control on IDT codecs

    Linus Torvalds
     
  • A small modification was necessary since in the machine description
    for 'n2cp' and 'ncp' nodes, there no longer is an 'intr' property.

    That's OK because this property was always nothing more than an
    array of integers '1' ... 'nr_inos + 1' so we can just compute it
    in-place.

    Signed-off-by: David S. Miller

    David S. Miller
     
  • And stop referring to Victoria Falls, as the attribute we're
    talking about is whether the rng is multi-unit capable which
    applies to several chip variants now.

    Signed-off-by: David S. Miller

    David S. Miller
     
  • The A0 revision of this chip is the only device that requires these
    features to be disabled.

    Signed-off-by: Matt Carlson
    Signed-off-by: David S. Miller

    Matt Carlson
     
  • The 5719 has bug where RDMAs larger than 4k can cause problems. This
    patch works around the problem by dividing larger DMA requests into
    something the hardware can handle.

    Signed-off-by: Matt Carlson
    Reviewed-by: Michael Chan
    Signed-off-by: David S. Miller

    Matt Carlson
     
  • As the driver breaks large skb fragments into smaller submissions to the
    hardware, there is a new danger that BDs might get exhausted before all
    fragments have been mapped. This patch adds code to make sure tx BDs
    aren't oversubscribed and flag the condition if it happens.

    Signed-off-by: Matt Carlson
    Reviewed-by: Michael Chan
    Signed-off-by: David S. Miller

    Matt Carlson
     
  • This patch consolidates all code that populates tx BDs into a single
    routine. Setting tx BDs needs to be more carefully controlled to see if
    workarounds need to be applied.

    Signed-off-by: Matt Carlson
    Reviewed-by: Michael Chan
    Signed-off-by: David S. Miller

    Matt Carlson
     
  • The following patches are going to break skb fragments into smaller
    sizes. This patch attempts to make the change easier to digest by only
    addressing the skb teardown portion.

    The patch modifies the driver to skip over any BDs that have a flag set
    that indicates the BD isn't the beginning of an skb fragment. Such BDs
    were a result of segmentation and do not need a pci_unmap_page() call.

    Signed-off-by: Matt Carlson
    Reviewed-by: Michael Chan
    Signed-off-by: David S. Miller

    Matt Carlson
     
  • In the following patches, unmapping skb fragments will get just as
    complicated as mapping them. This patch generalizes
    tg3_skb_error_unmap() and makes it the one-stop-shop for skb unmapping.

    Signed-off-by: Matt Carlson
    Reviewed-by: Michael Chan
    Signed-off-by: David S. Miller

    Matt Carlson
     
  • The first fragment of an skb should always be greater than 8 bytes.

    Signed-off-by: Matt Carlson
    Reviewed-by: Michael Chan
    Signed-off-by: David S. Miller

    Matt Carlson
     
  • In the following patches, the process the driver will use to assign skb
    fragments to transmit BDs will get more complicated. To prepare for
    that new code, this patch seeks to simplify how transmit BDs are
    populated. It does this by separating the code that assigns the BD
    members from the logic that controls how the fields are set.

    Signed-off-by: Matt Carlson
    Reviewed-by: Michael Chan
    Signed-off-by: David S. Miller

    Matt Carlson
     
  • The following patches will require the use of an additional flag in the
    ring_info structure. The use of this flag is tx path specific, so this
    patch defines a specialized ring_info structure.

    Signed-off-by: Matt Carlson
    Reviewed-by: Michael Chan
    Signed-off-by: David S. Miller

    Matt Carlson
     
  • The AX88772B uses only 11 bits of the header for the actual size. The other bits
    are used for something else. This causes dmesg full of messages:

    asix_rx_fixup() Bad Header Length

    This patch trims the check to only 11 bits. I believe on older chips, the
    remaining 5 top bits are unused.

    Signed-off-by: Marek Vasut
    Signed-off-by: David S. Miller

    Marek Vasut
     
  • Signed-off-by: Marek Vasut
    Signed-off-by: David S. Miller

    Marek Vasut
     
  • Try to send to correct address this time!

    ---------- Forwarded Message ----------

    Subject: [PATCH] Fix cdc-phonet build
    Date: Saturday 23 Jul 2011
    From: Chris Clayton
    To: linux-net@vger.kernel.org

    cdc-phonet does not presently build on linux-3.0 because there is no entry for it in
    drivers/net/Makefile. This patch adds that entry.

    Signed-off-by: Chris Clayton
    Signed-off-by: David S. Miller

    Chris Clayton
     
  • On Tue, Jul 26, 2011 at 05:40:27PM -0700, Joe Perches wrote:
    > On Tue, 2011-07-26 at 17:37 -0700, Jay Vosburgh wrote:
    > > Joe Perches wrote:
    > > >I'd prefer you don't separate the format string
    > > >into multiple pieces.
    > > Why not? To me, it looks easier to read split into sections
    > > that don't wrap lines.
    >
    > Harder to grep for a dmesg and the
    > defect rate of these split formats is
    > typically higher than single strings
    > because of bad spacing between string
    > segments.
    >

    I noticed that you took some time back in late 2009 to 'consolidate' the
    split format-strings present in the bonding driver at the time and I've
    decided I'm fine to leave them the way they are. The main point of my
    patch was to change the output and I would like to get that included.
    Here is my updated patch...

    Subject: [PATCH net-next-2.6 v2] bonding: reduce noise during init

    Many are using sysfs to configure bonding rather than module options, so
    there is no need for bonding to throw this warning in normal cases.

    Keep the message around when debugging is enabled as it might be useful
    for someone desperate enough to enable debugging, but eliminate it
    otherwise.

    Signed-off-by: Andy Gospodarek
    Signed-off-by: David S. Miller

    Andy Gospodarek
     
  • When a bond contains a device where one name is the subset of another
    (eth1 and eth10, for example), one cannot properly set the primary
    device or the currently active device.

    This was reported and based on work by Takuma Umeya. I also verified
    the problem and tested that this fix resolves it.

    V2: A few did not like the the current code or my changes, so I
    refactored bonding_store_primary and bonding_store_active_slave to be a
    bit cleaner, dropped the use of strnicmp since we did not really need
    the comparison to be case insensitive, and formatted the input string
    from sysfs so a comparison to IFNAMSIZ could be used.

    I also discovered an error in bonding_store_active_slave that would
    modify bond->primary_slave rather than bond->curr_active_slave before
    forcing the bonding driver to choose a new active slave.

    V3: Actually sending the proper patch....

    Signed-off-by: Andy Gospodarek
    Reported-by: Takuma Umeya
    Signed-off-by: David S. Miller

    Andy Gospodarek
     
  • After the last patch, We are left in a state in which only drivers calling
    ether_setup have IFF_TX_SKB_SHARING set (we assume that drivers touching real
    hardware call ether_setup for their net_devices and don't hold any state in
    their skbs. There are a handful of drivers that violate this assumption of
    course, and need to be fixed up. This patch identifies those drivers, and marks
    them as not being able to support the safe transmission of skbs by clearning the
    IFF_TX_SKB_SHARING flag in priv_flags

    Signed-off-by: Neil Horman
    CC: Karsten Keil
    CC: "David S. Miller"
    CC: Jay Vosburgh
    CC: Andy Gospodarek
    CC: Patrick McHardy
    CC: Krzysztof Halasa
    CC: "John W. Linville"
    CC: Greg Kroah-Hartman
    CC: Marcel Holtmann
    CC: Johannes Berg
    Signed-off-by: David S. Miller

    Neil Horman
     
  • Pktgen attempts to transmit shared skbs to net devices, which can't be used by
    some drivers as they keep state information in skbs. This patch adds a flag
    marking drivers as being able to handle shared skbs in their tx path. Drivers
    are defaulted to being unable to do so, but calling ether_setup enables this
    flag, as 90% of the drivers calling ether_setup touch real hardware and can
    handle shared skbs. A subsequent patch will audit drivers to ensure that the
    flag is set properly

    Signed-off-by: Neil Horman
    Reported-by: Jiri Pirko
    CC: Robert Olsson
    CC: Eric Dumazet
    CC: Alexey Dobriyan
    CC: David S. Miller
    Signed-off-by: David S. Miller

    Neil Horman
     
  • Signed-off-by: Eric Dumazet
    CC: Anton Blanchard
    Signed-off-by: David S. Miller

    Eric Dumazet
     
  • For some reason, when rxaccel is disabled, NV_RX3_VLAN_TAG_PRESENT is
    still set and some pseudorandom vids appear. So check for
    NETIF_F_HW_VLAN_RX as well. Also set correctly hw_features and set vlan
    mode on probe.

    Signed-off-by: Jiri Pirko
    Signed-off-by: David S. Miller

    Jiri Pirko
     
  • commit 87c288c6e9aa31720b72e2bc2d665e24e1653c3e "gianfar: do vlan cleanup" has two issues:
    # permutation of rx and tx flags
    # enabling vlan tag insertion by default (this leads to unusable connections on some configurations)

    If VLAN insertion is requested (via ethtool) it will be set at an other point ...

    Signed-off-by: Sebastian Poehn
    Signed-off-by: David S. Miller

    Sebastian Pöhn
     
  • David S. Miller