<feed xmlns='http://www.w3.org/2005/Atom'>
<title>talos-obmc-linux/drivers, branch v5.0.1</title>
<subtitle>Talos™ II Linux sources for OpenBMC</subtitle>
<id>https://git.raptorcs.com/git/talos-obmc-linux/atom?h=v5.0.1</id>
<link rel='self' href='https://git.raptorcs.com/git/talos-obmc-linux/atom?h=v5.0.1'/>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-obmc-linux/'/>
<updated>2019-03-10T06:09:01+00:00</updated>
<entry>
<title>Bluetooth: btrtl: Restore old logic to assume firmware is already loaded</title>
<updated>2019-03-10T06:09:01+00:00</updated>
<author>
<name>Kai-Heng Feng</name>
<email>kai.heng.feng@canonical.com</email>
</author>
<published>2019-01-27T08:33:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-obmc-linux/commit/?id=95b6840860ee06e1826ace0c30561d8b7703a838'/>
<id>urn:sha1:95b6840860ee06e1826ace0c30561d8b7703a838</id>
<content type='text'>
commit 00df214b1faae520880cc5c57e206f21239ef741 upstream.

Realtek bluetooth may not work after reboot:
[   12.446130] Bluetooth: hci0: RTL: rtl: unknown IC info, lmp subver a99e, hci rev 826c, hci ver 0008

This is a regression introduced by commit 26503ad25de8 ("Bluetooth:
btrtl: split the device initialization into smaller parts"). The new
logic errors out early when no matching IC info can be found, in this
case it means the firmware is already loaded.

So let's assume the firmware is already loaded when we can't find
matching IC info, like the old logic did.

Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=201921
Fixes: 26503ad25de8 ("Bluetooth: btrtl: split the device initialization into smaller parts")
Cc: stable@vger.kernel.org # 4.19+
Signed-off-by: Kai-Heng Feng &lt;kai.heng.feng@canonical.com&gt;
Signed-off-by: Marcel Holtmann &lt;marcel@holtmann.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>USB: serial: cp210x: fix GPIO in autosuspend</title>
<updated>2019-03-10T06:09:01+00:00</updated>
<author>
<name>Karoly Pados</name>
<email>pados@pados.hu</email>
</author>
<published>2019-02-17T17:59:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-obmc-linux/commit/?id=44c81a48231012e510267b9fe26403325465a19a'/>
<id>urn:sha1:44c81a48231012e510267b9fe26403325465a19a</id>
<content type='text'>
commit 7b0b644b9aa2de5032db0f468fddca091d0b7b90 upstream.

Current GPIO code in cp210x fails to take USB autosuspend into account,
making it practically impossible to use GPIOs with autosuspend enabled
without user configuration. Fix this like for ftdi_sio in a previous patch.
Tested on a CP2102N.

Signed-off-by: Karoly Pados &lt;pados@pados.hu&gt;
Fixes: cf5276ce7867 ("USB: serial: cp210x: Adding GPIO support for CP2105")
Cc: stable &lt;stable@vger.kernel.org&gt;
Signed-off-by: Johan Hovold &lt;johan@kernel.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>gnss: sirf: fix premature wakeup interrupt enable</title>
<updated>2019-03-10T06:09:01+00:00</updated>
<author>
<name>Johan Hovold</name>
<email>johan@kernel.org</email>
</author>
<published>2019-01-22T17:22:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-obmc-linux/commit/?id=02c66213c80ab85a78b494711d530ac20760efb2'/>
<id>urn:sha1:02c66213c80ab85a78b494711d530ac20760efb2</id>
<content type='text'>
commit 82f844c22588bf47132c82faeda50b6db473162c upstream.

Make sure the receiver is powered (and booted) before enabling the
wakeup interrupt to avoid spurious interrupts due to a floating input.

Similarly, disable the interrupt before powering off on probe errors and
on unbind.

Fixes: d2efbbd18b1e ("gnss: add driver for sirfstar-based receivers")
Cc: stable &lt;stable@vger.kernel.org&gt;	# 4.19
Signed-off-by: Johan Hovold &lt;johan@kernel.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>applicom: Fix potential Spectre v1 vulnerabilities</title>
<updated>2019-03-10T06:09:00+00:00</updated>
<author>
<name>Gustavo A. R. Silva</name>
<email>gustavo@embeddedor.com</email>
</author>
<published>2019-01-09T22:05:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-obmc-linux/commit/?id=46ce9ec42b78777900447bc4d79ab242b599a26c'/>
<id>urn:sha1:46ce9ec42b78777900447bc4d79ab242b599a26c</id>
<content type='text'>
commit d7ac3c6ef5d8ce14b6381d52eb7adafdd6c8bb3c upstream.

IndexCard is indirectly controlled by user-space, hence leading to
a potential exploitation of the Spectre variant 1 vulnerability.

This issue was detected with the help of Smatch:

drivers/char/applicom.c:418 ac_write() warn: potential spectre issue 'apbs' [r]
drivers/char/applicom.c:728 ac_ioctl() warn: potential spectre issue 'apbs' [r] (local cap)

Fix this by sanitizing IndexCard before using it to index apbs.

Notice that given that speculation windows are large, the policy is
to kill the speculation on the first load and not worry if it can be
completed with a dependent load/store [1].

[1] https://lore.kernel.org/lkml/20180423164740.GY17484@dhcp22.suse.cz/

Cc: stable@vger.kernel.org
Signed-off-by: Gustavo A. R. Silva &lt;gustavo@embeddedor.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>usb: xhci: Fix for Enabling USB ROLE SWITCH QUIRK on INTEL_SUNRISEPOINT_LP_XHCI</title>
<updated>2019-03-10T06:09:00+00:00</updated>
<author>
<name>Balaji Manoharan</name>
<email>m.balaji@intel.com</email>
</author>
<published>2019-02-20T17:50:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-obmc-linux/commit/?id=92424a6839151126bc925c4de05da90a7df23ece'/>
<id>urn:sha1:92424a6839151126bc925c4de05da90a7df23ece</id>
<content type='text'>
commit 8fde481ef3674ae5ad0dbfef4df18ff507c5675a upstream.

This fix enables USB role feature on intel commercial nuc
platform which is based on Kabylake chipset.

Signed-off-by: Balaji Manoharan &lt;m.balaji@intel.com&gt;
Reviewed-by: Hans de Goede &lt;hdegoede@redhat.com&gt;
Reviewed-by: Heikki Krogerus &lt;heikki.krogerus@linux.intel.com&gt;
Signed-off-by: Mathias Nyman &lt;mathias.nyman@linux.intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>xhci: tegra: Prevent error pointer dereference</title>
<updated>2019-03-10T06:09:00+00:00</updated>
<author>
<name>Thierry Reding</name>
<email>treding@nvidia.com</email>
</author>
<published>2019-02-20T13:48:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-obmc-linux/commit/?id=511ba5f2287c55f45a4bf45358cd5c06012c8d3c'/>
<id>urn:sha1:511ba5f2287c55f45a4bf45358cd5c06012c8d3c</id>
<content type='text'>
commit 0326ccb5feac6eac35ba6254260e2774277cd976 upstream.

During initialization, the host and super-speed power domains will
contain an ERR_PTR() encoded error code rather than being NULL. To
avoid a crash, use a !IS_ERR_OR_NULL() condition during cleanup.

Signed-off-by: Thierry Reding &lt;treding@nvidia.com&gt;
Fixes: 6494a9ad86de ("usb: xhci: tegra: Add genpd support")
Cc: stable &lt;stable@vger.kernel.org&gt;
Reviewed-by: Jon Hunter &lt;jonathanh@nvidia.com&gt;
Acked-by: Mathias Nyman &lt;mathias.nyman@linux.intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>team: Free BPF filter when unregistering netdev</title>
<updated>2019-03-10T06:09:00+00:00</updated>
<author>
<name>Ido Schimmel</name>
<email>idosch@mellanox.com</email>
</author>
<published>2019-03-03T07:35:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-obmc-linux/commit/?id=b0c649843a76cece77a569702a13183d9991c5d8'/>
<id>urn:sha1:b0c649843a76cece77a569702a13183d9991c5d8</id>
<content type='text'>
[ Upstream commit 692c31bd4054212312396b1d303bffab2c5b93a7 ]

When team is used in loadbalance mode a BPF filter can be used to
provide a hash which will determine the Tx port.

When the netdev is later unregistered the filter is not freed which
results in memory leaks [1].

Fix by freeing the program and the corresponding filter when
unregistering the netdev.

[1]
unreferenced object 0xffff8881dbc47cc8 (size 16):
  comm "teamd", pid 3068, jiffies 4294997779 (age 438.247s)
  hex dump (first 16 bytes):
    a3 00 6b 6b 6b 6b 6b 6b 88 a5 82 e1 81 88 ff ff  ..kkkkkk........
  backtrace:
    [&lt;000000008a3b47e3&gt;] team_nl_cmd_options_set+0x88f/0x11b0
    [&lt;00000000c4f4f27e&gt;] genl_family_rcv_msg+0x78f/0x1080
    [&lt;00000000610ef838&gt;] genl_rcv_msg+0xca/0x170
    [&lt;00000000a281df93&gt;] netlink_rcv_skb+0x132/0x380
    [&lt;000000004d9448a2&gt;] genl_rcv+0x29/0x40
    [&lt;000000000321b2f4&gt;] netlink_unicast+0x4c0/0x690
    [&lt;000000008c25dffb&gt;] netlink_sendmsg+0x929/0xe10
    [&lt;00000000068298c5&gt;] sock_sendmsg+0xc8/0x110
    [&lt;0000000082a61ff0&gt;] ___sys_sendmsg+0x77a/0x8f0
    [&lt;00000000663ae29d&gt;] __sys_sendmsg+0xf7/0x250
    [&lt;0000000027c5f11a&gt;] do_syscall_64+0x14d/0x610
    [&lt;000000006cfbc8d3&gt;] entry_SYSCALL_64_after_hwframe+0x49/0xbe
    [&lt;00000000e23197e2&gt;] 0xffffffffffffffff
unreferenced object 0xffff8881e182a588 (size 2048):
  comm "teamd", pid 3068, jiffies 4294997780 (age 438.247s)
  hex dump (first 32 bytes):
    20 00 00 00 02 00 00 00 30 00 00 00 28 f0 ff ff   .......0...(...
    07 00 00 00 00 00 00 00 28 00 00 00 00 00 00 00  ........(.......
  backtrace:
    [&lt;000000002daf01fb&gt;] lb_bpf_func_set+0x45c/0x6d0
    [&lt;000000008a3b47e3&gt;] team_nl_cmd_options_set+0x88f/0x11b0
    [&lt;00000000c4f4f27e&gt;] genl_family_rcv_msg+0x78f/0x1080
    [&lt;00000000610ef838&gt;] genl_rcv_msg+0xca/0x170
    [&lt;00000000a281df93&gt;] netlink_rcv_skb+0x132/0x380
    [&lt;000000004d9448a2&gt;] genl_rcv+0x29/0x40
    [&lt;000000000321b2f4&gt;] netlink_unicast+0x4c0/0x690
    [&lt;000000008c25dffb&gt;] netlink_sendmsg+0x929/0xe10
    [&lt;00000000068298c5&gt;] sock_sendmsg+0xc8/0x110
    [&lt;0000000082a61ff0&gt;] ___sys_sendmsg+0x77a/0x8f0
    [&lt;00000000663ae29d&gt;] __sys_sendmsg+0xf7/0x250
    [&lt;0000000027c5f11a&gt;] do_syscall_64+0x14d/0x610
    [&lt;000000006cfbc8d3&gt;] entry_SYSCALL_64_after_hwframe+0x49/0xbe
    [&lt;00000000e23197e2&gt;] 0xffffffffffffffff

Fixes: 01d7f30a9f96 ("team: add loadbalance mode")
Signed-off-by: Ido Schimmel &lt;idosch@mellanox.com&gt;
Reported-by: Amit Cohen &lt;amitc@mellanox.com&gt;
Acked-by: Jiri Pirko &lt;jiri@mellanox.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>sky2: Disable MSI on Dell Inspiron 1545 and Gateway P-79</title>
<updated>2019-03-10T06:08:59+00:00</updated>
<author>
<name>Kai-Heng Feng</name>
<email>kai.heng.feng@canonical.com</email>
</author>
<published>2019-03-04T07:00:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-obmc-linux/commit/?id=3445d44b8330ab2219f3fb77d453c6068f11406c'/>
<id>urn:sha1:3445d44b8330ab2219f3fb77d453c6068f11406c</id>
<content type='text'>
[ Upstream commit b33b7cd6fd86478dd2890a9abeb6f036aa01fdf7 ]

Some sky2 chips fire IRQ after S3, before the driver is fully resumed:
[ 686.804877] do_IRQ: 1.37 No irq handler for vector

This is likely a platform bug that device isn't fully quiesced during
S3. Use MSI-X, maskable MSI or INTx can prevent this issue from
happening.

Since MSI-X and maskable MSI are not supported by this device, fallback
to use INTx on affected platforms.

BugLink: https://bugs.launchpad.net/bugs/1807259
BugLink: https://bugs.launchpad.net/bugs/1809843
Signed-off-by: Kai-Heng Feng &lt;kai.heng.feng@canonical.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>qmi_wwan: Add support for Quectel EG12/EM12</title>
<updated>2019-03-10T06:08:59+00:00</updated>
<author>
<name>Kristian Evensen</name>
<email>kristian.evensen@gmail.com</email>
</author>
<published>2019-03-02T12:32:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-obmc-linux/commit/?id=43610748b73d309c17276a2042d94e6fa06df27e'/>
<id>urn:sha1:43610748b73d309c17276a2042d94e6fa06df27e</id>
<content type='text'>
[ Upstream commit 822e44b45eb991c63487c5e2ce7d636411870a8d ]

Quectel EG12 (module)/EM12 (M.2 card) is a Cat. 12 LTE modem. The modem
behaves in the same way as the EP06, so the "set DTR"-quirk must be
applied and the diagnostic-interface check performed. Since the
diagnostic-check now applies to more modems, I have renamed the function
from quectel_ep06_diag_detected() to quectel_diag_detected().

Signed-off-by: Kristian Evensen &lt;kristian.evensen@gmail.com&gt;
Acked-by: Bjørn Mork &lt;bjorn@mork.no&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>net: mscc: Enable all ports in QSGMII</title>
<updated>2019-03-10T06:08:59+00:00</updated>
<author>
<name>Kavya Sree Kotagiri</name>
<email>kavyasree.kotagiri@microchip.com</email>
</author>
<published>2019-02-28T07:32:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/talos-obmc-linux/commit/?id=e1c9e3fe2d343758f189cd682c3b23cdd4f20601'/>
<id>urn:sha1:e1c9e3fe2d343758f189cd682c3b23cdd4f20601</id>
<content type='text'>
[ Upstream commit 084e5bb16bd7dc2b551bbd9fb358bf73e03ee8d8 ]

When Ocelot phy-mode is QSGMII, all 4 ports involved in
QSGMII shall be kept out of reset and
Tx lanes shall be enabled to pass the data.

Fixes: a556c76adc05 ("net: mscc: Add initial Ocelot switch support")
Signed-off-by: Kavya Sree Kotagiri &lt;kavyasree.kotagiri@microchip.com&gt;
Signed-off-by: Steen Hegelund &lt;Steen.Hegelund@microchip.com&gt;
Co-developed-by: Steen Hegelund &lt;Steen.Hegelund@microchip.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
</feed>
