<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/sound/core/seq, branch linux-5.0.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.0.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-5.0.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2019-04-17T06:39:47Z</updated>
<entry>
<title>ALSA: seq: Fix OOB-reads from strlcpy</title>
<updated>2019-04-17T06:39:47Z</updated>
<author>
<name>Zubin Mithra</name>
</author>
<published>2019-04-04T21:33:55Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=df828c33163f2e5f651be384ccc0baf2236a95b5'/>
<id>urn:sha1:df828c33163f2e5f651be384ccc0baf2236a95b5</id>
<content type='text'>
commit 212ac181c158c09038c474ba68068be49caecebb upstream.

When ioctl calls are made with non-null-terminated userspace strings,
strlcpy causes an OOB-read from within strlen. Fix by changing to use
strscpy instead.

Signed-off-by: Zubin Mithra &lt;zsm@chromium.org&gt;
Reviewed-by: Guenter Roeck &lt;groeck@chromium.org&gt;
Cc: &lt;stable@vger.kernel.org&gt;
Signed-off-by: Takashi Iwai &lt;tiwai@suse.de&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>ALSA: seq: oss: Fix Spectre v1 vulnerability</title>
<updated>2019-04-03T04:27:29Z</updated>
<author>
<name>Gustavo A. R. Silva</name>
</author>
<published>2019-03-20T23:42:01Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=a30c0ff829c63ebf8fe399e0860f32db0bd7acfe'/>
<id>urn:sha1:a30c0ff829c63ebf8fe399e0860f32db0bd7acfe</id>
<content type='text'>
commit c709f14f0616482b67f9fbcb965e1493a03ff30b upstream.

dev 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:

sound/core/seq/oss/seq_oss_synth.c:626 snd_seq_oss_synth_make_info() warn: potential spectre issue 'dp-&gt;synths' [w] (local cap)

Fix this by sanitizing dev before using it to index dp-&gt;synths.

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: Takashi Iwai &lt;tiwai@suse.de&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

</content>
</entry>
<entry>
<title>Remove 'type' argument from access_ok() function</title>
<updated>2019-01-04T02:57:57Z</updated>
<author>
<name>Linus Torvalds</name>
</author>
<published>2019-01-04T02:57:57Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=96d4f267e40f9509e8a66e2b39e8b95655617693'/>
<id>urn:sha1:96d4f267e40f9509e8a66e2b39e8b95655617693</id>
<content type='text'>
Nobody has actually used the type (VERIFY_READ vs VERIFY_WRITE) argument
of the user address range verification function since we got rid of the
old racy i386-only code to walk page tables by hand.

It existed because the original 80386 would not honor the write protect
bit when in kernel mode, so you had to do COW by hand before doing any
user access.  But we haven't supported that in a long time, and these
days the 'type' argument is a purely historical artifact.

A discussion about extending 'user_access_begin()' to do the range
checking resulted this patch, because there is no way we're going to
move the old VERIFY_xyz interface to that model.  And it's best done at
the end of the merge window when I've done most of my merges, so let's
just get this done once and for all.

This patch was mostly done with a sed-script, with manual fix-ups for
the cases that weren't of the trivial 'access_ok(VERIFY_xyz' form.

There were a couple of notable cases:

 - csky still had the old "verify_area()" name as an alias.

 - the iter_iov code had magical hardcoded knowledge of the actual
   values of VERIFY_{READ,WRITE} (not that they mattered, since nothing
   really used it)

 - microblaze used the type argument for a debug printout

but other than those oddities this should be a total no-op patch.

I tried to fix up all architectures, did fairly extensive grepping for
access_ok() uses, and the changes are trivial, but I may have missed
something.  Any missed conversion should be trivially fixable, though.

Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>ALSA: seq: oss: Use the standard fall-through annotation</title>
<updated>2018-10-12T07:31:29Z</updated>
<author>
<name>Takashi Iwai</name>
</author>
<published>2018-10-04T17:59:41Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e8c92251a8351f9550a9e20a47364d0a20f28d95'/>
<id>urn:sha1:e8c92251a8351f9550a9e20a47364d0a20f28d95</id>
<content type='text'>
As a preparatory patch for the upcoming -Wimplicit-fallthrough
compiler checks, replace with the standard "fall through" annotation.
Unfortunately gcc doesn't understand a chattier text.

Signed-off-by: Takashi Iwai &lt;tiwai@suse.de&gt;
</content>
</entry>
<entry>
<title>ALSA: rawmidi: A lightweight function to discard pending bytes</title>
<updated>2018-10-04T18:13:17Z</updated>
<author>
<name>Takashi Iwai</name>
</author>
<published>2018-09-13T06:20:43Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=6aea5702e27ebc85747d6e4943a0c378e1752be0'/>
<id>urn:sha1:6aea5702e27ebc85747d6e4943a0c378e1752be0</id>
<content type='text'>
For discarding the pending bytes on rawmidi, we process with a loop of
snd_rawmidi_transmit() which is just a waste of CPU power.
Implement a lightweight API function to discard the pending bytes and
the proceed the ring buffer instantly, and use it instead of open
codes.

Signed-off-by: Takashi Iwai &lt;tiwai@suse.de&gt;
</content>
</entry>
<entry>
<title>ALSA: seq: Do error checks at creating system ports</title>
<updated>2018-08-28T10:52:02Z</updated>
<author>
<name>Takashi Iwai</name>
</author>
<published>2018-08-28T10:49:43Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b8e131542b47b81236ecf6768c923128e1f5db6e'/>
<id>urn:sha1:b8e131542b47b81236ecf6768c923128e1f5db6e</id>
<content type='text'>
snd_seq_system_client_init() doesn't check the errors returned from
its port creations.  Let's do it properly and handle the error paths.

Signed-off-by: Takashi Iwai &lt;tiwai@suse.de&gt;
</content>
</entry>
<entry>
<title>ALSA: seq: add error check in snd_seq_system_client_init()</title>
<updated>2018-08-28T09:06:11Z</updated>
<author>
<name>Dan Carpenter</name>
</author>
<published>2018-08-28T08:46:34Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c4f1957e14444e444b35418e85069b7ab65465a5'/>
<id>urn:sha1:c4f1957e14444e444b35418e85069b7ab65465a5</id>
<content type='text'>
Static checkers complain that snd_seq_create_kernel_client() can return
-EBUSY here so we need to have some error handling.

Signed-off-by: Dan Carpenter &lt;dan.carpenter@oracle.com&gt;
Signed-off-by: Takashi Iwai &lt;tiwai@suse.de&gt;
</content>
</entry>
<entry>
<title>ALSA: seq: virmidi: Fix discarding the unsubscribed output</title>
<updated>2018-08-14T20:50:52Z</updated>
<author>
<name>Takashi Iwai</name>
</author>
<published>2018-08-14T19:27:51Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=82fd4b05d704623a0e4aa7fda48e272a9889337d'/>
<id>urn:sha1:82fd4b05d704623a0e4aa7fda48e272a9889337d</id>
<content type='text'>
The recent change to move the virmidi output processing to a work
slightly modified the code to discard the unsubscribed outputs so that
it works without a temporary buffer.  However, this is actually buggy,
and may spew a kernel warning due to the unexpected call of
snd_rawmidi_transmit_ack(), as triggered by syzbot.

This patch takes back to the original code in that part, use a
temporary buffer and simply repeat snd_rawmidi_transmit(), in order to
address the regression.

Fixes: f7debfe54090 ("ALSA: seq: virmidi: Offload the output event processing")
Reported-by: syzbot+ec5f605c91812d200367@syzkaller.appspotmail.com
Signed-off-by: Takashi Iwai &lt;tiwai@suse.de&gt;
</content>
</entry>
<entry>
<title>ALSA: seq_oss: Mark expected switch fall-through</title>
<updated>2018-08-04T06:30:45Z</updated>
<author>
<name>Gustavo A. R. Silva</name>
</author>
<published>2018-08-03T20:53:54Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=eb2caeb88c181904110f8e74995c7b0bb7fd39f6'/>
<id>urn:sha1:eb2caeb88c181904110f8e74995c7b0bb7fd39f6</id>
<content type='text'>
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.

Warning level 2 was used: -Wimplicit-fallthrough=2

Signed-off-by: Gustavo A. R. Silva &lt;gustavo@embeddedor.com&gt;
Signed-off-by: Takashi Iwai &lt;tiwai@suse.de&gt;
</content>
</entry>
<entry>
<title>ALSA: seq: Mark expected switch fall-through</title>
<updated>2018-08-04T06:30:36Z</updated>
<author>
<name>Gustavo A. R. Silva</name>
</author>
<published>2018-08-03T20:52:33Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=2f3b94e539a46052f8eba1f295ff5646e227578a'/>
<id>urn:sha1:2f3b94e539a46052f8eba1f295ff5646e227578a</id>
<content type='text'>
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.

Notice that in this particular case, I replaced the code comment with
a proper "fall through" annotation, which is what GCC is expecting
to find.

Signed-off-by: Gustavo A. R. Silva &lt;gustavo@embeddedor.com&gt;
Signed-off-by: Takashi Iwai &lt;tiwai@suse.de&gt;
</content>
</entry>
</feed>
