<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers, branch v3.6</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
</subtitle>
<id>https://git.shady.money/linux/atom?h=v3.6</id>
<link rel='self' href='https://git.shady.money/linux/atom?h=v3.6'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/'/>
<updated>2012-09-29T17:37:04Z</updated>
<entry>
<title>Merge tag 'iommu-fixes-v3.6-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu</title>
<updated>2012-09-29T17:37:04Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2012-09-29T17:37:04Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=6a3e3dbee62a8fcf13c349b141b3cedf35a65c41'/>
<id>urn:sha1:6a3e3dbee62a8fcf13c349b141b3cedf35a65c41</id>
<content type='text'>
Pull IOMMU fixes from Joerg Roedel:
 "Two small patches:

	* One patch to fix the function declarations for
	  !CONFIG_IOMMU_API. This is causing build errors
	  in linux-next and should be fixed for v3.6.

	* Another patch to fix an IOMMU group related NULL pointer
	  dereference."

* tag 'iommu-fixes-v3.6-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu:
  iommu/amd: Fix wrong assumption in iommu-group specific code
  iommu: static inline iommu group stub functions
</content>
</entry>
<entry>
<title>Merge git://git.infradead.org/users/willy/linux-nvme</title>
<updated>2012-09-29T17:31:52Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2012-09-29T17:31:52Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=21e98932dcf15fe7eabd09a35f2020e0dd86b685'/>
<id>urn:sha1:21e98932dcf15fe7eabd09a35f2020e0dd86b685</id>
<content type='text'>
Pull NVMe driver fixes from Matthew Wilcox:
 "Now that actual hardware has been released (don't have any yet
  myself), people are starting to want some of these fixes merged."

Willy doesn't have hardware? Guys...

* git://git.infradead.org/users/willy/linux-nvme:
  NVMe: Cancel outstanding IOs on queue deletion
  NVMe: Free admin queue memory on initialisation failure
  NVMe: Use ida for nvme device instance
  NVMe: Fix whitespace damage in nvme_init
  NVMe: handle allocation failure in nvme_map_user_pages()
  NVMe: Fix uninitialized iod compiler warning
  NVMe: Do not set IO queue depth beyond device max
  NVMe: Set block queue max sectors
  NVMe: use namespace id for nvme_get_features
  NVMe: replace nvme_ns with nvme_dev for user admin
  NVMe: Fix nvme module init when nvme_major is set
  NVMe: Set request queue logical block size
</content>
</entry>
<entry>
<title>mtdchar: fix offset overflow detection</title>
<updated>2012-09-28T19:13:46Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2012-09-08T19:57:30Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=9c603e53d380459fb62fec7cd085acb0b74ac18f'/>
<id>urn:sha1:9c603e53d380459fb62fec7cd085acb0b74ac18f</id>
<content type='text'>
Sasha Levin has been running trinity in a KVM tools guest, and was able
to trigger the BUG_ON() at arch/x86/mm/pat.c:279 (verifying the range of
the memory type).  The call trace showed that it was mtdchar_mmap() that
created an invalid remap_pfn_range().

The problem is that mtdchar_mmap() does various really odd and subtle
things with the vma page offset etc, and uses the wrong types (and the
wrong overflow) detection for it.

For example, the page offset may well be 32-bit on a 32-bit
architecture, but after shifting it up by PAGE_SHIFT, we need to use a
potentially 64-bit resource_size_t to correctly hold the full value.

Also, we need to check that the vma length plus offset doesn't overflow
before we check that it is smaller than the length of the mtdmap region.

This fixes things up and tries to make the code a bit easier to read.

Reported-and-tested-by: Sasha Levin &lt;levinsasha928@gmail.com&gt;
Acked-by: Suresh Siddha &lt;suresh.b.siddha@intel.com&gt;
Acked-by: Artem Bityutskiy &lt;dedekind1@gmail.com&gt;
Cc: David Woodhouse &lt;dwmw2@infradead.org&gt;
Cc: linux-mtd@lists.infradead.org
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net</title>
<updated>2012-09-28T17:09:33Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2012-09-28T17:09:33Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=6672d90fe779dc0dfffe027c3ede12609df091c2'/>
<id>urn:sha1:6672d90fe779dc0dfffe027c3ede12609df091c2</id>
<content type='text'>
Pull networking fixes from David S Miller:

 1) Netfilter xt_limit module can use uninitialized rules, from Jan
    Engelhardt.

 2) Wei Yongjun has found several more spots where error pointers were
    treated as NULL/non-NULL and vice versa.

 3) bnx2x was converted to pci_io{,un}map() but one remaining plain
    iounmap() got missed.  From Neil Horman.

 4) Due to a fence-post type error in initialization of inetpeer entries
    (which is where we store the ICMP rate limiting information), we can
    erroneously drop ICMPs if the inetpeer was created right around when
    jiffies wraps.

    Fix from Nicolas Dichtel.

 5) smsc75xx resume fix from Steve Glendinnig.

 6) LAN87xx smsc chips need an explicit hardware init, from Marek Vasut.

 7) qlcnic uses msleep() with locks held, fix from Narendra K.

* git://git.kernel.org/pub/scm/linux/kernel/git/davem/net:
  netdev: octeon: fix return value check in octeon_mgmt_init_phy()
  inetpeer: fix token initialization
  qlcnic: Fix scheduling while atomic bug
  bnx2: Clean up remaining iounmap
  net: phy: smsc: Implement PHY config_init for LAN87xx
  smsc75xx: fix resume after device reset
  netdev: pasemi: fix return value check in pasemi_mac_phy_init()
  team: fix return value check
  l2tp: fix return value check
  netfilter: xt_limit: have r-&gt;cost != 0 case work
</content>
</entry>
<entry>
<title>Merge tag 'dm-3.6-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/agk/linux-dm</title>
<updated>2012-09-28T17:00:01Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2012-09-28T17:00:01Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=c3a086e638e0cf76b26f6053a096354980af9396'/>
<id>urn:sha1:c3a086e638e0cf76b26f6053a096354980af9396</id>
<content type='text'>
Pull dm fixes from Alasdair G Kergon:
 "A few fixes for problems discovered during the 3.6 cycle.

  Of particular note, are fixes to the thin target's discard support,
  which I hope is finally working correctly; and fixes for multipath
  ioctls and device limits when there are no paths."

* tag 'dm-3.6-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/agk/linux-dm:
  dm verity: fix overflow check
  dm thin: fix discard support for data devices
  dm thin: tidy discard support
  dm: retain table limits when swapping to new table with no devices
  dm table: clear add_random unless all devices have it set
  dm: handle requests beyond end of device instead of using BUG_ON
  dm mpath: only retry ioctl when no paths if queue_if_no_path set
  dm thin: do not set discard_zeroes_data
</content>
</entry>
<entry>
<title>iommu/amd: Fix wrong assumption in iommu-group specific code</title>
<updated>2012-09-28T14:14:44Z</updated>
<author>
<name>Joerg Roedel</name>
<email>joerg.roedel@amd.com</email>
</author>
<published>2012-09-28T14:14:44Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=0774e392555a128cff7a94929b9ce957927fef49'/>
<id>urn:sha1:0774e392555a128cff7a94929b9ce957927fef49</id>
<content type='text'>
The new IOMMU groups code in the AMD IOMMU driver makes the
assumption that there is a pci_dev struct available for all
device-ids listed in the IVRS ACPI table. Unfortunatly this
assumption is not true and so this code causes a NULL
pointer dereference at boot on some systems.

Fix it by making sure the given pointer is never NULL when
passed to the group specific code. The real fix is larger
and will be queued for v3.7.

Reported-by: Florian Dazinger &lt;florian@dazinger.net&gt;
Signed-off-by: Joerg Roedel &lt;joerg.roedel@amd.com&gt;
</content>
</entry>
<entry>
<title>netdev: octeon: fix return value check in octeon_mgmt_init_phy()</title>
<updated>2012-09-28T05:18:32Z</updated>
<author>
<name>Wei Yongjun</name>
<email>yongjun_wei@trendmicro.com.cn</email>
</author>
<published>2012-09-27T19:04:21Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=df555b665367f9de6c04826acc482096f17c243d'/>
<id>urn:sha1:df555b665367f9de6c04826acc482096f17c243d</id>
<content type='text'>
In case of error, the function of_phy_connect() returns NULL
pointer not ERR_PTR(). The IS_ERR() test in the return value
check should be replaced with NULL test.

dpatch engine is used to auto generate this patch.
(https://github.com/weiyj/dpatch)

Signed-off-by: Wei Yongjun &lt;yongjun_wei@trendmicro.com.cn&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>Merge branch 'drm-fixes' of git://people.freedesktop.org/~airlied/linux</title>
<updated>2012-09-27T23:51:14Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2012-09-27T23:51:14Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=63994137eb53bb0fc42ad180c0ce509d3eb3bdc9'/>
<id>urn:sha1:63994137eb53bb0fc42ad180c0ce509d3eb3bdc9</id>
<content type='text'>
Pull drm fixes from Dave Airlie:
 "The three nouveau fixes quiten unneeded dmesg spam that people are
   seeing and pondering,

  The udl fix stops it from trying to driver monitors that are too big,
  where we get a black screen.

  And a vmware memory alloc problem."

* 'drm-fixes' of git://people.freedesktop.org/~airlied/linux:
  drm/nvc0/fifo: ignore bits in PFIFO_INTR that aren't set in PFIFO_INTR_EN
  drm/udl: limit modes to the sku pixel limits.
  vmwgfx: corruption in vmw_event_fence_action_create()
  drm/nvc0/ltcg: mask off intr 0x10
  drm/nouveau: silence a debug message triggered by newer userspace
</content>
</entry>
<entry>
<title>Merge tag 'usb-3.6-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb</title>
<updated>2012-09-27T23:49:15Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2012-09-27T23:49:15Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=a31fb6988a37f46f3a677aa5bc982094f3a03567'/>
<id>urn:sha1:a31fb6988a37f46f3a677aa5bc982094f3a03567</id>
<content type='text'>
Pull USB fixes from Greg Kroah-Hartman:
 "Here are two USB bugfixes for your 3.6-rc7 tree.

  The OHCI fix has been reported a number of times and is a regression
  from 3.5, and the patch that causes the regression was on the way to
  the -stable trees before I was reminded (again) that this fix needed
  to get to your tree soon.

  The host controller bugfix was reported in older kernels as being
  pretty easy to trigger, and has been tested by Red Hat and their
  customers.

  Both have been in the usb-next branch in the -next tree for a while
  now, I just cherry-picked them out to get to you in time for the 3.6
  release.

  Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;"

* tag 'usb-3.6-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb:
  USB: Fix race condition when removing host controllers
  USB: ohci-at91: fix null pointer in ohci_hcd_at91_overcurrent_irq
</content>
</entry>
<entry>
<title>qlcnic: Fix scheduling while atomic bug</title>
<updated>2012-09-27T23:24:52Z</updated>
<author>
<name>Narendra K</name>
<email>narendra_k@dell.com</email>
</author>
<published>2012-09-25T07:53:19Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=68b3f28c11bf896be32ad2a2e151aaa5f4a7c98e'/>
<id>urn:sha1:68b3f28c11bf896be32ad2a2e151aaa5f4a7c98e</id>
<content type='text'>
In the device close path, 'qlcnic_fw_destroy_ctx' and
'qlcnic_poll_rsp' call msleep. But  'qlcnic_fw_destroy_ctx' and
'qlcnic_poll_rsp' are called with 'adapter-&gt;tx_clean_lock' spin lock
held resulting in scheduling while atomic bug causing the following
trace.

I observed that the commit 012dc19a45b2b9cc2ebd14aaa401cf782c2abba4
from John Fastabend addresses a similar issue in ixgbevf driver.
Adopting the same approach used in the commit, this patch uses mdelay
to address the issue.

[79884.999115] BUG: scheduling while atomic: ip/30846/0x00000002
[79885.005562] INFO: lockdep is turned off.
[79885.009958] Modules linked in: qlcnic fuse nf_conntrack_netbios_ns nf_conntrack_broadcast ipt_MASQUERADE bnep bluetooth rfkill ip6table_mangle ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables iptable_nat nf_nat iptable_mangle ipt_REJECT nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter ip_tables dcdbas coretemp kvm_intel kvm iTCO_wdt ixgbe iTCO_vendor_support crc32c_intel ghash_clmulni_intel nfsd microcode sb_edac pcspkr edac_core dca bnx2x shpchp auth_rpcgss nfs_acl lpc_ich mfd_core mdio lockd libcrc32c wmi acpi_pad acpi_power_meter sunrpc uinput sd_mod sr_mod cdrom crc_t10dif ahci libahci libata megaraid_sas usb_storage dm_mirror dm_region_hash dm_log dm_mod [last unloaded: qlcnic]
[79885.083608] Pid: 30846, comm: ip Tainted: G        W  O 3.6.0-rc7+ #1
[79885.090805] Call Trace:
[79885.093569]  [&lt;ffffffff816764d8&gt;] __schedule_bug+0x68/0x76
[79885.099699]  [&lt;ffffffff8168358e&gt;] __schedule+0x99e/0xa00
[79885.105634]  [&lt;ffffffff81683929&gt;] schedule+0x29/0x70
[79885.111186]  [&lt;ffffffff81680def&gt;] schedule_timeout+0x16f/0x350
[79885.117724]  [&lt;ffffffff811afb7a&gt;] ? init_object+0x4a/0x90
[79885.123770]  [&lt;ffffffff8107c190&gt;] ? __internal_add_timer+0x140/0x140
[79885.130873]  [&lt;ffffffff81680fee&gt;] schedule_timeout_uninterruptible+0x1e/0x20
[79885.138773]  [&lt;ffffffff8107e830&gt;] msleep+0x20/0x30
[79885.144159]  [&lt;ffffffffa04c7fbf&gt;] qlcnic_issue_cmd+0xef/0x290 [qlcnic]
[79885.151478]  [&lt;ffffffffa04c8265&gt;] qlcnic_fw_cmd_destroy_rx_ctx+0x55/0x90 [qlcnic]
[79885.159868]  [&lt;ffffffffa04c92fd&gt;] qlcnic_fw_destroy_ctx+0x2d/0xa0 [qlcnic]
[79885.167576]  [&lt;ffffffffa04bf2ed&gt;] __qlcnic_down+0x11d/0x180 [qlcnic]
[79885.174708]  [&lt;ffffffffa04bf6f8&gt;] qlcnic_close+0x18/0x20 [qlcnic]
[79885.181547]  [&lt;ffffffff8153b4c5&gt;] __dev_close_many+0x95/0xe0
[79885.187899]  [&lt;ffffffff8153b548&gt;] __dev_close+0x38/0x50
[79885.193761]  [&lt;ffffffff81545101&gt;] __dev_change_flags+0xa1/0x180
[79885.200419]  [&lt;ffffffff81545298&gt;] dev_change_flags+0x28/0x70
[79885.206779]  [&lt;ffffffff815531b8&gt;] do_setlink+0x378/0xa00
[79885.212731]  [&lt;ffffffff81354fe1&gt;] ? nla_parse+0x31/0xe0
[79885.218612]  [&lt;ffffffff815558ee&gt;] rtnl_newlink+0x37e/0x560
[79885.224768]  [&lt;ffffffff812cfa19&gt;] ? selinux_capable+0x39/0x50
[79885.231217]  [&lt;ffffffff812cbf98&gt;] ? security_capable+0x18/0x20
[79885.237765]  [&lt;ffffffff81555114&gt;] rtnetlink_rcv_msg+0x114/0x2f0
[79885.244412]  [&lt;ffffffff81551f87&gt;] ? rtnl_lock+0x17/0x20
[79885.250280]  [&lt;ffffffff81551f87&gt;] ? rtnl_lock+0x17/0x20
[79885.256148]  [&lt;ffffffff81555000&gt;] ? __rtnl_unlock+0x20/0x20
[79885.262413]  [&lt;ffffffff81570fc1&gt;] netlink_rcv_skb+0xa1/0xb0
[79885.268661]  [&lt;ffffffff81551fb5&gt;] rtnetlink_rcv+0x25/0x40
[79885.274727]  [&lt;ffffffff815708bd&gt;] netlink_unicast+0x19d/0x220
[79885.281146]  [&lt;ffffffff81570c45&gt;] netlink_sendmsg+0x305/0x3f0
[79885.287595]  [&lt;ffffffff8152b188&gt;] ? sock_update_classid+0x148/0x2e0
[79885.294650]  [&lt;ffffffff81525c2c&gt;] sock_sendmsg+0xbc/0xf0
[79885.300600]  [&lt;ffffffff8152600c&gt;] __sys_sendmsg+0x3ac/0x3c0
[79885.306853]  [&lt;ffffffff8109be23&gt;] ? up_read+0x23/0x40
[79885.312510]  [&lt;ffffffff816896cc&gt;] ? do_page_fault+0x2bc/0x570
[79885.318968]  [&lt;ffffffff81191854&gt;] ? sys_brk+0x44/0x150
[79885.324715]  [&lt;ffffffff811c458c&gt;] ? fget_light+0x24c/0x520
[79885.330875]  [&lt;ffffffff815286f9&gt;] sys_sendmsg+0x49/0x90
[79885.336707]  [&lt;ffffffff8168e429&gt;] system_call_fastpath+0x16/0x1b

Signed-off-by: Narendra K &lt;narendra_k@dell.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
</feed>
