<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux, branch v3.14.7</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/?h=v3.14.7</id>
<link rel='self' href='https://git.amat.us/linux/atom/?h=v3.14.7'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2014-06-11T19:02:49Z</updated>
<entry>
<title>Linux 3.14.7</title>
<updated>2014-06-11T19:02:49Z</updated>
<author>
<name>Greg Kroah-Hartman</name>
<email>gregkh@linuxfoundation.org</email>
</author>
<published>2014-06-11T19:02:49Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=fce5b5fc495819be9eef7d4d41a9659b2968c7ea'/>
<id>urn:sha1:fce5b5fc495819be9eef7d4d41a9659b2968c7ea</id>
<content type='text'>
</content>
</entry>
<entry>
<title>iommu/vt-d: Fix missing IOTLB flush in intel_iommu_unmap()</title>
<updated>2014-06-11T18:54:14Z</updated>
<author>
<name>David Woodhouse</name>
<email>dwmw2@infradead.org</email>
</author>
<published>2014-06-09T13:09:53Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=51d20e1096a711f8cfa9d98a3ac2dd2c7c0fc20c'/>
<id>urn:sha1:51d20e1096a711f8cfa9d98a3ac2dd2c7c0fc20c</id>
<content type='text'>
Based on commit ea8ea460c9ace60bbb5ac6e5521d637d5c15293d upstream

This missing IOTLB flush was added as a minor, inconsequential bug-fix
in commit ea8ea460c ("iommu/vt-d: Clean up and fix page table clear/free
behaviour") in 3.15. It wasn't originally intended for -stable but a
couple of users have reported issues which turn out to be fixed by
adding the missing flush.

Signed-off-by: David Woodhouse &lt;David.Woodhouse@intel.com&gt;
</content>
</entry>
<entry>
<title>gpio: mcp23s08: Bug fix of SPI device tree registration.</title>
<updated>2014-06-11T18:54:14Z</updated>
<author>
<name>Michael Welling</name>
<email>mwelling@ieee.org</email>
</author>
<published>2014-04-17T01:00:24Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=f10acdb935fa79b48719e0a7bf284b7c1e5bf776'/>
<id>urn:sha1:f10acdb935fa79b48719e0a7bf284b7c1e5bf776</id>
<content type='text'>
commit 99e4b98dbe3ad1fe38a74d12c3b8d44a55930de4 upstream.

The chips variable needs to be incremented for each chip that is
found in the spi_present_mask when registering via device tree.
Without this and the checking a negative index is passed to the
data-&gt;chip array in a subsequent loop.

Signed-off-by: Michael Welling &lt;mwelling@ieee.org&gt;
Acked-by: Peter Korsgaard &lt;peter@korsgaard.com&gt;
Signed-off-by: Linus Walleij &lt;linus.walleij@linaro.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>drm/i915: dp: fix order of dp aux i2c device cleanup</title>
<updated>2014-06-11T18:54:14Z</updated>
<author>
<name>Imre Deak</name>
<email>imre.deak@intel.com</email>
</author>
<published>2014-02-11T15:12:49Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=3af2e71643df2f603bea99a7e0e13afbf9ea6d78'/>
<id>urn:sha1:3af2e71643df2f603bea99a7e0e13afbf9ea6d78</id>
<content type='text'>
commit 80f65de3c9b8101c1613fa82df500ba6a099a11c upstream.

Atm we set the parent of the dp i2c device to be the correspondig
connector device. During driver cleanup we first remove the connector
device through intel_modeset_cleanup()-&gt;drm_sysfs_connector_remove() and
only after that the i2c device through the encoder's destroy callback.
This order is not supported by the device core and we'll get a warning,
see the below bugzilla ticket. The proper order is to remove first any
child device and only then the parent device.

The first part of the fix changes the i2c device's parent to be the drm
device. Its logical owner is not the connector anyway, but the encoder.
Since the encoder doesn't have a device object, the next best choice is
the drm device. This is the same what we do in the case of the sdvo i2c
device and what the nouveau driver does.

The second part creates a symlink in the connector's sysfs directory
pointing to the i2c device. This is so, that we keep the current ABI,
which also makes sense in case someone wants to look up the i2c device
belonging to a specific connector.

Reference: http://lists.freedesktop.org/archives/intel-gfx/2014-January/038782.html
Reference: http://lists.freedesktop.org/archives/intel-gfx/2014-February/039427.html
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=70523
Signed-off-by: Imre Deak &lt;imre.deak@intel.com&gt;
Reviewed-by: Antti Koskipää &lt;antti.koskipaa@linux.intel.com&gt;
Signed-off-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
Cc: Jani Nikula &lt;jani.nikula@intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>drm/i915: add unregister callback to connector</title>
<updated>2014-06-11T18:54:14Z</updated>
<author>
<name>Imre Deak</name>
<email>imre.deak@intel.com</email>
</author>
<published>2014-02-11T15:12:48Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=19eab47618d2e89f4c8d071c24d3f0f4b62363cd'/>
<id>urn:sha1:19eab47618d2e89f4c8d071c24d3f0f4b62363cd</id>
<content type='text'>
commit 4932e2c3c716067f3580e1a9687bed9d751549e3 upstream.

Since

commit d9255d57147e1dbcebdf6670409c2fa0ac3609e6
Author: Paulo Zanoni &lt;paulo.r.zanoni@intel.com&gt;
Date:   Thu Sep 26 20:05:59 2013 -0300

it became clear that we need to separate the unload sequence into two
parts:

1. remove all interfaces through which new operations on some object
   (crtc, encoder, connector) can be started and make sure all pending
   operations are completed
2. do the actual tear down of the internal representation of the above
   objects

The above commit achieved this separation for connectors by splitting
out the sysfs removal part from the connector's destroy callback and
doing this removal before calling drm_mode_config_cleanup() which does
the actual tear-down of all the drm objects.

Since we'll have to customize the interface removal part for different
types of connectors in the upcoming patches, add a new unregister
callback and move the interface removal part to it.

No functional change.

Signed-off-by: Imre Deak &lt;imre.deak@intel.com&gt;
Reviewed-by: Antti Koskipää &lt;antti.koskipaa@linux.intel.com&gt;
Signed-off-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
Cc: Jani Nikula &lt;jani.nikula@intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>netfilter: nfnetlink: Fix use after free when it fails to process batch</title>
<updated>2014-06-11T18:54:14Z</updated>
<author>
<name>Denys Fedoryshchenko</name>
<email>nuclearcat@nuclearcat.com</email>
</author>
<published>2014-05-04T11:35:37Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=07e8687141e5073ff7931666982232bdc4bc3400'/>
<id>urn:sha1:07e8687141e5073ff7931666982232bdc4bc3400</id>
<content type='text'>
commit ecd15dd7e45f3683fa8142b9f2c015dfaa0c243d upstream.

This bug manifests when calling the nft command line tool without
nf_tables kernel support.

kernel message:
[   44.071555] Netfilter messages via NETLINK v0.30.
[   44.072253] BUG: unable to handle kernel NULL pointer dereference at 0000000000000119
[   44.072264] IP: [&lt;ffffffff8171db1f&gt;] netlink_getsockbyportid+0xf/0x70
[   44.072272] PGD 7f2b74067 PUD 7f2b73067 PMD 0
[   44.072277] Oops: 0000 [#1] SMP
[...]
[   44.072369] Call Trace:
[   44.072373]  [&lt;ffffffff8171fd81&gt;] netlink_unicast+0x91/0x200
[   44.072377]  [&lt;ffffffff817206c9&gt;] netlink_ack+0x99/0x110
[   44.072381]  [&lt;ffffffffa004b951&gt;] nfnetlink_rcv+0x3c1/0x408 [nfnetlink]
[   44.072385]  [&lt;ffffffff8171fde3&gt;] netlink_unicast+0xf3/0x200
[   44.072389]  [&lt;ffffffff817201ef&gt;] netlink_sendmsg+0x2ff/0x740
[   44.072394]  [&lt;ffffffff81044752&gt;] ? __mmdrop+0x62/0x90
[   44.072398]  [&lt;ffffffff816dafdb&gt;] sock_sendmsg+0x8b/0xc0
[   44.072403]  [&lt;ffffffff812f1af5&gt;] ? copy_user_enhanced_fast_string+0x5/0x10
[   44.072406]  [&lt;ffffffff816dbb6c&gt;] ? move_addr_to_kernel+0x2c/0x50
[   44.072410]  [&lt;ffffffff816db423&gt;] ___sys_sendmsg+0x3c3/0x3d0
[   44.072415]  [&lt;ffffffff811301ba&gt;] ? handle_mm_fault+0xa9a/0xc60
[   44.072420]  [&lt;ffffffff811362d6&gt;] ? mmap_region+0x166/0x5a0
[   44.072424]  [&lt;ffffffff817da84c&gt;] ? __do_page_fault+0x1dc/0x510
[   44.072428]  [&lt;ffffffff812b8b2c&gt;] ? apparmor_capable+0x1c/0x60
[   44.072435]  [&lt;ffffffff817d6e9a&gt;] ? _raw_spin_unlock_bh+0x1a/0x20
[   44.072439]  [&lt;ffffffff816dfc86&gt;] ? release_sock+0x106/0x150
[   44.072443]  [&lt;ffffffff816dc212&gt;] __sys_sendmsg+0x42/0x80
[   44.072446]  [&lt;ffffffff816dc262&gt;] SyS_sendmsg+0x12/0x20
[   44.072450]  [&lt;ffffffff817df616&gt;] system_call_fastpath+0x1a/0x1f

Signed-off-by: Denys Fedoryshchenko &lt;nuclearcat@nuclearcat.com&gt;
Signed-off-by: Pablo Neira Ayuso &lt;pablo@netfilter.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>netfilter: Fix potential use after free in ip6_route_me_harder()</title>
<updated>2014-06-11T18:54:14Z</updated>
<author>
<name>Sergey Popovich</name>
<email>popovich_sergei@mail.ru</email>
</author>
<published>2014-05-08T13:22:35Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=64db35627759552fe11de45d3787737a6fe9a3af'/>
<id>urn:sha1:64db35627759552fe11de45d3787737a6fe9a3af</id>
<content type='text'>
commit a8951d5814e1373807a94f79f7ccec7041325470 upstream.

Dst is released one line before we access it again with dst-&gt;error.

Fixes: 58e35d147128 netfilter: ipv6: propagate routing errors from
ip6_route_me_harder()

Signed-off-by: Sergey Popovich &lt;popovich_sergei@mail.ru&gt;
Signed-off-by: Pablo Neira Ayuso &lt;pablo@netfilter.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>target: Fix alua_access_state attribute OOPs for un-configured devices</title>
<updated>2014-06-11T18:54:13Z</updated>
<author>
<name>Nicholas Bellinger</name>
<email>nab@linux-iscsi.org</email>
</author>
<published>2014-06-06T07:52:57Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=fed542cfe4ed6077767b9e1dcf6bf2bc73c115b6'/>
<id>urn:sha1:fed542cfe4ed6077767b9e1dcf6bf2bc73c115b6</id>
<content type='text'>
commit f1453773514bb8b0bba0716301e8c8f17f8d39c7 upstream.

This patch fixes a OOPs where an attempt to write to the per-device
alua_access_state configfs attribute at:

  /sys/kernel/config/target/core/$HBA/$DEV/alua/$TG_PT_GP/alua_access_state

results in an NULL pointer dereference when the backend device has not
yet been configured.

This patch adds an explicit check for DF_CONFIGURED, and fails with
-ENODEV to avoid this case.

Reported-by: Chris Boot &lt;crb@tiger-computing.co.uk&gt;
Reported-by: Philip Gaw &lt;pgaw@darktech.org.uk&gt;
Cc: Chris Boot &lt;crb@tiger-computing.co.uk&gt;
Cc: Philip Gaw &lt;pgaw@darktech.org.uk&gt;
Signed-off-by: Nicholas Bellinger &lt;nab@linux-iscsi.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>iscsi-target: Fix wrong buffer / buffer overrun in iscsi_change_param_value()</title>
<updated>2014-06-11T18:54:13Z</updated>
<author>
<name>Roland Dreier</name>
<email>roland@purestorage.com</email>
</author>
<published>2014-05-29T20:32:30Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=d0473df3f2efb211493f6150c6d88c0d132131e4'/>
<id>urn:sha1:d0473df3f2efb211493f6150c6d88c0d132131e4</id>
<content type='text'>
commit 79d59d08082dd0a0a18f8ceb78c99f9f321d72aa upstream.

In non-leading connection login, iscsi_login_non_zero_tsih_s1() calls
iscsi_change_param_value() with the buffer it uses to hold the login
PDU, not a temporary buffer.  This leads to the login header getting
corrupted and login failing for non-leading connections in MC/S.

Fix this by adding a wrapper iscsi_change_param_sprintf() that handles
the temporary buffer itself to avoid confusion.  Also handle sending a
reject in case of failure in the wrapper, which lets the calling code
get quite a bit smaller and easier to read.

Finally, bump the size of the temporary buffer from 32 to 64 bytes to be
safe, since "MaxRecvDataSegmentLength=" by itself is 25 bytes; with a
trailing NUL, a value &gt;= 1M will lead to a buffer overrun.  (This isn't
the default but we don't need to run right at the ragged edge here)

Reported-by: Santosh Kulkarni &lt;santosh.kulkarni@calsoftinc.com&gt;
Signed-off-by: Roland Dreier &lt;roland@purestorage.com&gt;
Signed-off-by: Nicholas Bellinger &lt;nab@linux-iscsi.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>iser-target: Add missing target_put_sess_cmd for ImmedateData failure</title>
<updated>2014-06-11T18:54:13Z</updated>
<author>
<name>Nicholas Bellinger</name>
<email>nab@linux-iscsi.org</email>
</author>
<published>2014-05-23T07:48:35Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=eca33548a672a6ad6d5add846885f76d33f4c4b3'/>
<id>urn:sha1:eca33548a672a6ad6d5add846885f76d33f4c4b3</id>
<content type='text'>
commit 6cc44a6fb46e1ecc1c28125aa8fa34d317aa9ea7 upstream.

This patch addresses a bug where an early exception for SCSI WRITE
with ImmediateData=Yes was missing the target_put_sess_cmd() call
to drop the extra se_cmd-&gt;cmd_kref reference obtained during the
normal iscsit_setup_scsi_cmd() codepath execution.

This bug was manifesting itself during session shutdown within
isert_cq_rx_comp_err() where target_wait_for_sess_cmds() would
end up waiting indefinately for the last se_cmd-&gt;cmd_kref put to
occur for the failed SCSI WRITE + ImmediateData descriptors.

This fix follows what traditional iscsi-target code already does
for the same failure case within iscsit_get_immediate_data().

Reported-by: Sagi Grimberg &lt;sagig@dev.mellanox.co.il&gt;
Cc: Sagi Grimberg &lt;sagig@dev.mellanox.co.il&gt;
Cc: Or Gerlitz &lt;ogerlitz@mellanox.com&gt;
Signed-off-by: Nicholas Bellinger &lt;nab@linux-iscsi.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
</feed>
