~vicamo/+git/ubuntu-kernel:bug-1861610/add-more-lenovo-elan-i2c-ids/focal

Last commit made on 2020-03-27
Get this branch:
git clone -b bug-1861610/add-more-lenovo-elan-i2c-ids/focal https://git.launchpad.net/~vicamo/+git/ubuntu-kernel
Only You-Sheng Yang can upload to this branch. If you are You-Sheng Yang please log in for upload directions.

Branch merges

Branch information

Name:
bug-1861610/add-more-lenovo-elan-i2c-ids/focal
Repository:
lp:~vicamo/+git/ubuntu-kernel

Recent commits

9b4310f... by You-Sheng Yang

Bug 1861610: add more hardware ID for Lenovo laptop

41f07d3... by "Dave.Wang" <email address hidden>

Input: elan_i2c - add more hardware ID for Lenovo laptop

Signed-off-by: Dave Wang <email address hidden>
(cherry picked from
https://lore.kernel.org/linux-input/000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw/)
Signed-off-by: You-Sheng Yang <email address hidden>

18e4e93... by Andrea Righi

UBUNTU: SAUCE: selftests/seccomp -- Disable timeout for seccomp tests

These tests have subtests which are timing out in autopkgtest.
Disable the timeout to prevent this.

Signed-off-by: Andrea Righi <email address hidden>

eb5147d... by Andrea Righi

UBUNTU: SAUCE: kselftest/runner: avoid using timeout if timeout is disabled

Avoid using /usr/bin/timeout unnecessarily if timeout is set to 0 in the
"settings" file for a specific test.

NOTE: this change prevents a syscall_restart failure in the seccomp
kselftest.

Signed-off-by: Andrea Righi <email address hidden>

602ed1a... by Kamal Mostafa

UBUNTU: upstream stable to v5.4.28

BugLink: https://bugs.launchpad.net/bugs/1869061

Ignore: yes
Signed-off-by: Kamal Mostafa <email address hidden>

bfd4761... by Greg Kroah-Hartman <email address hidden>

Linux 5.4.28

BugLink: https://bugs.launchpad.net/bugs/1869061

Signed-off-by: Kamal Mostafa <email address hidden>

b9f699f... by Johan Hovold <email address hidden>

staging: greybus: loopback_test: fix potential path truncations

BugLink: https://bugs.launchpad.net/bugs/1869061

commit ae62cf5eb2792d9a818c2d93728ed92119357017 upstream.

Newer GCC warns about possible truncations of two generated path names as
we're concatenating the configurable sysfs and debugfs path prefixes
with a filename and placing the results in buffers of the same size as
the maximum length of the prefixes.

 snprintf(d->name, MAX_STR_LEN, "gb_loopback%u", dev_id);

 snprintf(d->sysfs_entry, MAX_SYSFS_PATH, "%s%s/",
   t->sysfs_prefix, d->name);

 snprintf(d->debugfs_entry, MAX_SYSFS_PATH, "%sraw_latency_%s",
   t->debugfs_prefix, d->name);

Fix this by separating the maximum path length from the maximum prefix
length and reducing the latter enough to fit the generated strings.

Note that we also need to reduce the device-name buffer size as GCC
isn't smart enough to figure out that we ever only used MAX_STR_LEN
bytes of it.

Fixes: 6b0658f68786 ("greybus: tools: Add tools directory to greybus repo and add loopback")
Signed-off-by: Johan Hovold <email address hidden>
Link: https://<email address hidden>
Signed-off-by: Greg Kroah-Hartman <email address hidden>
Signed-off-by: Kamal Mostafa <email address hidden>

e499acb... by Johan Hovold <email address hidden>

staging: greybus: loopback_test: fix potential path truncation

BugLink: https://bugs.launchpad.net/bugs/1869061

commit f16023834863932f95dfad13fac3fc47f77d2f29 upstream.

Newer GCC warns about a possible truncation of a generated sysfs path
name as we're concatenating a directory path with a file name and
placing the result in a buffer that is half the size of the maximum
length of the directory path (which is user controlled).

loopback_test.c: In function 'open_poll_files':
loopback_test.c:651:31: warning: '%s' directive output may be truncated writing up to 511 bytes into a region of size 255 [-Wformat-truncation=]
  651 | snprintf(buf, sizeof(buf), "%s%s", dev->sysfs_entry, "iteration_count");
      | ^~
loopback_test.c:651:3: note: 'snprintf' output between 16 and 527 bytes into a destination of size 255
  651 | snprintf(buf, sizeof(buf), "%s%s", dev->sysfs_entry, "iteration_count");
      | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Fix this by making sure the buffer is large enough the concatenated
strings.

Fixes: 6b0658f68786 ("greybus: tools: Add tools directory to greybus repo and add loopback")
Fixes: 9250c0ee2626 ("greybus: Loopback_test: use poll instead of inotify")
Signed-off-by: Johan Hovold <email address hidden>
Link: https://<email address hidden>
Signed-off-by: Greg Kroah-Hartman <email address hidden>
Signed-off-by: Kamal Mostafa <email address hidden>

2e11a51... by Jernej Skrabec <email address hidden>

drm/bridge: dw-hdmi: fix AVI frame colorimetry

BugLink: https://bugs.launchpad.net/bugs/1869061

commit e8dca30f7118461d47e1c3510d0e31b277439151 upstream.

CTA-861-F explicitly states that for RGB colorspace colorimetry should
be set to "none". Fix that.

Acked-by: Laurent Pinchart <email address hidden>
Fixes: def23aa7e982 ("drm: bridge: dw-hdmi: Switch to V4L bus format and encodings")
Signed-off-by: Jernej Skrabec <email address hidden>
Link: https://patchwork.freedesktop<email address hidden>
Signed-off-by: Greg Kroah-Hartman <email address hidden>
Signed-off-by: Kamal Mostafa <email address hidden>

8da1a7a... by Sagi Grimberg <email address hidden>

nvmet-tcp: set MSG_MORE only if we actually have more to send

BugLink: https://bugs.launchpad.net/bugs/1869061

commit 98fd5c723730f560e5bea919a64ac5b83d45eb72 upstream.

When we send PDU data, we want to optimize the tcp stack
operation if we have more data to send. So when we set MSG_MORE
when:
- We have more fragments coming in the batch, or
- We have a more data to send in this PDU
- We don't have a data digest trailer
- We optimize with the SUCCESS flag and omit the NVMe completion
  (used if sq_head pointer update is disabled)

This addresses a regression in QD=1 with SUCCESS flag optimization
as we unconditionally set MSG_MORE when we didn't actually have
more data to send.

Fixes: 70583295388a ("nvmet-tcp: implement C2HData SUCCESS optimization")
Reported-by: Mark Wunderlich <email address hidden>
Tested-by: Mark Wunderlich <email address hidden>
Signed-off-by: Sagi Grimberg <email address hidden>
Signed-off-by: Keith Busch <email address hidden>
Signed-off-by: Greg Kroah-Hartman <email address hidden>
Signed-off-by: Kamal Mostafa <email address hidden>