<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel, branch linux-3.14.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.</subtitle>
<id>https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-3.14.y</id>
<link rel='self' href='https://universe.0xinfinity.dev/distro/kernel/atom?h=linux-3.14.y'/>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/'/>
<updated>2016-09-11T08:00:18Z</updated>
<entry>
<title>Linux 3.14.79</title>
<updated>2016-09-11T08:00:18Z</updated>
<author>
<name>Greg Kroah-Hartman</name>
<email>gregkh@linuxfoundation.org</email>
</author>
<published>2016-09-11T08:00:18Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=b65f2f457c49b2cfd7967c34b7a0b04c25587f13'/>
<id>urn:sha1:b65f2f457c49b2cfd7967c34b7a0b04c25587f13</id>
<content type='text'>
</content>
</entry>
<entry>
<title>mm: thp: fix SMP race condition between THP page fault and MADV_DONTNEED</title>
<updated>2016-09-11T07:59:59Z</updated>
<author>
<name>Andrea Arcangeli</name>
<email>aarcange@redhat.com</email>
</author>
<published>2016-02-26T23:19:28Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=09a2499466dc69d1e54e8e879d4591cdd0ca17c8'/>
<id>urn:sha1:09a2499466dc69d1e54e8e879d4591cdd0ca17c8</id>
<content type='text'>
commit ad33bb04b2a6cee6c1f99fabb15cddbf93ff0433 upstream.

pmd_trans_unstable()/pmd_none_or_trans_huge_or_clear_bad() were
introduced to locklessy (but atomically) detect when a pmd is a regular
(stable) pmd or when the pmd is unstable and can infinitely transition
from pmd_none() and pmd_trans_huge() from under us, while only holding
the mmap_sem for reading (for writing not).

While holding the mmap_sem only for reading, MADV_DONTNEED can run from
under us and so before we can assume the pmd to be a regular stable pmd
we need to compare it against pmd_none() and pmd_trans_huge() in an
atomic way, with pmd_trans_unstable().  The old pmd_trans_huge() left a
tiny window for a race.

Useful applications are unlikely to notice the difference as doing
MADV_DONTNEED concurrently with a page fault would lead to undefined
behavior.

[js] 3.12 backport: no pmd_devmap in 3.12 yet.

[akpm@linux-foundation.org: tidy up comment grammar/layout]
Signed-off-by: Andrea Arcangeli &lt;aarcange@redhat.com&gt;
Reported-by: Kirill A. Shutemov &lt;kirill.shutemov@linux.intel.com&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
Cc: Vlastimil Babka &lt;vbabka@suse.cz&gt;
Signed-off-by: Jiri Slaby &lt;jslaby@suse.cz&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;


</content>
</entry>
<entry>
<title>fix d_walk()/non-delayed __d_free() race</title>
<updated>2016-09-11T07:59:58Z</updated>
<author>
<name>Willy Tarreau</name>
<email>w@1wt.eu</email>
</author>
<published>2016-08-27T09:31:35Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=7cac57a69919afdf3bdda5242afdd535b2d9a2b0'/>
<id>urn:sha1:7cac57a69919afdf3bdda5242afdd535b2d9a2b0</id>
<content type='text'>
I checked Jari's explanation below and found that v3.14.77 and v3.12.62
are missing the same fix as 3.10. In fact Al's original commit 3d56c25
("fix d_walk()/non-delayed __d_free() race") used to mention to check 
this __d_materialise_dentry() function in the Cc: stable line, but this
got lost during the backports.

Normally all of our 3 kernels need to apply the following patch that
Ben correctly put in 3.16 and 3.2. I'm fixing the backport in 3.10.103
right now.

On Mon, Aug 22, 2016 at 04:56:57PM +0300, Jari Ruusu wrote:
&gt; This patch for 3.10 branch appears to be missing one important
&gt; 
&gt; +       dentry-&gt;d_flags |= DCACHE_RCUACCESS;
&gt; 
&gt; in fs/dcache.c __d_materialise_dentry() function. When Ben Hutchings
&gt; backported Al Viro's original fix to stable branches that he maintains,
&gt; he added that one additional line to both 3.2 and 3.16 branches. Please
&gt; consider including that additional one line fix for 3.10 stable branch
&gt; also.
&gt; 
&gt; 
&gt; Ben Hutchings said this on his 3.2.82-rc1 patch:
&gt; [bwh: Backported to 3.2:
&gt;  - Adjust context
&gt;  - Also set the flag in __d_materialise_dentry())]
&gt; 
&gt; http://marc.info/?l=linux-kernel&amp;m=147117565612275&amp;w=2
&gt; 
&gt; 
&gt; Ben Hutchings said this on his 3.16.37-rc1 patch:
&gt; [bwh: Backported to 3.16:
&gt;  - Adjust context
&gt;  - Also set the flag in __d_materialise_dentry())]
&gt; 
&gt; http://marc.info/?l=linux-kernel&amp;m=147117433412006&amp;w=2
&gt; 
&gt; 
&gt; Also mentioned by Sasha Levin on 3.18 and 4.1 commits:
&gt; Cc: stable@vger.kernel.org # v3.2+ (and watch out for __d_materialise_dentry())
&gt; 
&gt; http://marc.info/?l=linux-stable-commits&amp;m=146648034410827&amp;w=2
&gt; http://marc.info/?l=linux-stable-commits&amp;m=146647471009771&amp;w=2


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

</content>
</entry>
<entry>
<title>s390/sclp_ctl: fix potential information leak with /dev/sclp</title>
<updated>2016-09-11T07:59:58Z</updated>
<author>
<name>Martin Schwidefsky</name>
<email>schwidefsky@de.ibm.com</email>
</author>
<published>2016-04-25T15:54:28Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=78a4260f1fad5cfc6ad7cf6e01a93a2fed0d0e3e'/>
<id>urn:sha1:78a4260f1fad5cfc6ad7cf6e01a93a2fed0d0e3e</id>
<content type='text'>
commit 532c34b5fbf1687df63b3fcd5b2846312ac943c6 upstream.

The sclp_ctl_ioctl_sccb function uses two copy_from_user calls to
retrieve the sclp request from user space. The first copy_from_user
fetches the length of the request which is stored in the first two
bytes of the request. The second copy_from_user gets the complete
sclp request, but this copies the length field a second time.
A malicious user may have changed the length in the meantime.

Reported-by: Pengfei Wang &lt;wpengfeinudt@gmail.com&gt;
Reviewed-by: Michael Holzheu &lt;holzheu@linux.vnet.ibm.com&gt;
Signed-off-by: Martin Schwidefsky &lt;schwidefsky@de.ibm.com&gt;
Signed-off-by: Juerg Haefliger &lt;juerg.haefliger@hpe.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>rds: fix an infoleak in rds_inc_info_copy</title>
<updated>2016-09-11T07:59:58Z</updated>
<author>
<name>Kangjie Lu</name>
<email>kangjielu@gmail.com</email>
</author>
<published>2016-06-02T08:11:20Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=d57906c6850c5bb9a93841da3deb6df53135d133'/>
<id>urn:sha1:d57906c6850c5bb9a93841da3deb6df53135d133</id>
<content type='text'>
commit 4116def2337991b39919f3b448326e21c40e0dbb upstream.

The last field "flags" of object "minfo" is not initialized.
Copying this object out may leak kernel stack data.
Assign 0 to it to avoid leak.

Signed-off-by: Kangjie Lu &lt;kjlu@gatech.edu&gt;
Acked-by: Santosh Shilimkar &lt;santosh.shilimkar@oracle.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Juerg Haefliger &lt;juerg.haefliger@hpe.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>staging: comedi: ni_mio_common: fix wrong insn_write handler</title>
<updated>2016-09-11T07:59:58Z</updated>
<author>
<name>Ian Abbott</name>
<email>abbotti@mev.co.uk</email>
</author>
<published>2016-09-07T14:33:12Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=f842188c4f4f63a5b6fb59f45ac121162c0ab4c4'/>
<id>urn:sha1:f842188c4f4f63a5b6fb59f45ac121162c0ab4c4</id>
<content type='text'>
commit 5ca05345c56cb979e1a25ab6146437002f95cac8 upstream.

For counter subdevices, the `s-&gt;insn_write` handler is being set to the
wrong function, `ni_tio_insn_read()`.  It should be
`ni_tio_insn_write()`.

Signed-off-by: Ian Abbott &lt;abbotti@mev.co.uk&gt;
Reported-by: Éric Piel &lt;piel@delmic.com&gt;
Fixes: 10f74377eec3 ("staging: comedi: ni_tio: make ni_tio_winsn() a proper comedi (*insn_write)")
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>ext4: validate that metadata blocks do not overlap superblock</title>
<updated>2016-09-11T07:59:58Z</updated>
<author>
<name>Theodore Ts'o</name>
<email>tytso@mit.edu</email>
</author>
<published>2016-08-01T04:51:02Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=553a1f6d027a8e0c59ca7bbe0f26a25d1881cfef'/>
<id>urn:sha1:553a1f6d027a8e0c59ca7bbe0f26a25d1881cfef</id>
<content type='text'>
commit 829fa70dddadf9dd041d62b82cd7cea63943899d upstream.

A number of fuzzing failures seem to be caused by allocation bitmaps
or other metadata blocks being pointed at the superblock.

This can cause kernel BUG or WARNings once the superblock is
overwritten, so validate the group descriptor blocks to make sure this
doesn't happen.

Signed-off-by: Theodore Ts'o &lt;tytso@mit.edu&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>stb6100: fix buffer length check in stb6100_write_reg_range()</title>
<updated>2016-09-11T07:59:58Z</updated>
<author>
<name>Alexander Shiyan</name>
<email>shc_work@mail.ru</email>
</author>
<published>2014-02-26T02:41:14Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=a6e226c25157082a043cce63d14ecab68fdcc433'/>
<id>urn:sha1:a6e226c25157082a043cce63d14ecab68fdcc433</id>
<content type='text'>
commit 7e6bd12fb77b0067df13fb3ba3fadbdff2945396 upstream.

We are checking sizeof() the wrong variable!

Signed-off-by: Alexander Shiyan &lt;shc_work@mail.ru&gt;
Signed-off-by: Michael Krufky &lt;mkrufky@linuxtv.org&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;m.chehab@samsung.com&gt;
Cc: Willy Tarreau &lt;w@1wt.eu&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>ALSA: oxygen: Fix logical-not-parentheses warning</title>
<updated>2016-09-11T07:59:58Z</updated>
<author>
<name>Tomer Barletz</name>
<email>barletz@gmail.com</email>
</author>
<published>2015-08-02T09:08:57Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=7ae8ffd384be9159cf057affd17caf2a687f493f'/>
<id>urn:sha1:7ae8ffd384be9159cf057affd17caf2a687f493f</id>
<content type='text'>
commit 8ec7cfce3762299ae289c384e281b2f4010ae231 upstream.

This fixes the following warning, that is seen with gcc 5.1:
warning: logical not is only applied to the left hand side of comparison [-Wlogical-not-parentheses].

Signed-off-by: Tomer Barletz &lt;barletz@gmail.com&gt;
Signed-off-by: Takashi Iwai &lt;tiwai@suse.de&gt;
Cc: Willy Tarreau &lt;w@1wt.eu&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>HID: hid-input: Add parentheses to quell gcc warning</title>
<updated>2016-09-11T07:59:58Z</updated>
<author>
<name>James C Boyd</name>
<email>jcboyd.dev@gmail.com</email>
</author>
<published>2015-05-27T22:09:06Z</published>
<link rel='alternate' type='text/html' href='https://universe.0xinfinity.dev/distro/kernel/commit/?id=ac98961e44fa5df4383f0a60f0c4923f368da1d8'/>
<id>urn:sha1:ac98961e44fa5df4383f0a60f0c4923f368da1d8</id>
<content type='text'>
commit 09a5c34e8d6b05663ec4c3d22b1fbd9fec89aaf9 upstream.

GCC reports a -Wlogical-not-parentheses warning here; therefore
add parentheses to shut it up and to express our intent more.

Signed-off-by: James C Boyd &lt;jcboyd.dev@gmail.com&gt;
Signed-off-by: Jiri Kosina &lt;jkosina@suse.cz&gt;
Cc: Willy Tarreau &lt;w@1wt.eu&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

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