20 Jan, 2021
2 commits
-
This is the 5.10.7 stable release
* tag 'v5.10.7': (144 commits)
Linux 5.10.7
scsi: target: Fix XCOPY NAA identifier lookup
rtlwifi: rise completion at the last step of firmware callback
...Signed-off-by: Jason Liu
-
This is the 5.10.5 stable release
* tag 'v5.10.5': (63 commits)
Linux 5.10.5
device-dax: Fix range release
ext4: avoid s_mb_prefetch to be zero in individual scenarios
...Signed-off-by: Jason Liu
13 Jan, 2021
2 commits
-
To unify the driver interface on 8q and 8m,
we need to add a new header file to define custom interfacesSigned-off-by: Ming Qian
Reviewed-by: Shijie Qin
(cherry picked from commit 47c536bc846dfec04cf5eb502b895a65ecd5376d) -
commit b16671e8f493e3df40b1fb0dff4078f391c5099a upstream.
When large bucket feature was added, BCH_FEATURE_INCOMPAT_LARGE_BUCKET
was introduced into the incompat feature set. It used bucket_size_hi
(which was added at the tail of struct cache_sb_disk) to extend current
16bit bucket size to 32bit with existing bucket_size in struct
cache_sb_disk.This is not a good idea, there are two obvious problems,
- Bucket size is always value power of 2, if store log2(bucket size) in
existing bucket_size of struct cache_sb_disk, it is unnecessary to add
bucket_size_hi.
- Macro csum_set() assumes d[SB_JOURNAL_BUCKETS] is the last member in
struct cache_sb_disk, bucket_size_hi was added after d[] which makes
csum_set calculate an unexpected super block checksum.To fix the above problems, this patch introduces a new incompat feature
bit BCH_FEATURE_INCOMPAT_LOG_LARGE_BUCKET_SIZE, when this bit is set, it
means bucket_size in struct cache_sb_disk stores the order of power-of-2
bucket size value. When user specifies a bucket size larger than 32768
sectors, BCH_FEATURE_INCOMPAT_LOG_LARGE_BUCKET_SIZE will be set to
incompat feature set, and bucket_size stores log2(bucket size) more
than store the real bucket size value.The obsoleted BCH_FEATURE_INCOMPAT_LARGE_BUCKET won't be used anymore,
it is renamed to BCH_FEATURE_INCOMPAT_OBSO_LARGE_BUCKET and still only
recognized by kernel driver for legacy compatible purpose. The previous
bucket_size_hi is renmaed to obso_bucket_size_hi in struct cache_sb_disk
and not used in bcache-tools anymore.For cache device created with BCH_FEATURE_INCOMPAT_LARGE_BUCKET feature,
bcache-tools and kernel driver still recognize the feature string and
display it as "obso_large_bucket".With this change, the unnecessary extra space extend of bcache on-disk
super block can be avoided, and csum_set() may generate expected check
sum as well.Fixes: ffa470327572 ("bcache: add bucket_size_hi into struct cache_sb_disk for large bucket")
Signed-off-by: Coly Li
Cc: stable@vger.kernel.org # 5.9+
Signed-off-by: Jens Axboe
Signed-off-by: Greg Kroah-Hartman
06 Jan, 2021
1 commit
-
commit a85cbe6159ffc973e5702f70a3bd5185f8f3c38d upstream.
and include in UAPI headers instead of .
The reason is to avoid indirect include when using
some network headers: or others ->
-> .This indirect include causes on MUSL redefinition of struct sysinfo when
included both and some of UAPI headers:In file included from x86_64-buildroot-linux-musl/sysroot/usr/include/linux/kernel.h:5,
from x86_64-buildroot-linux-musl/sysroot/usr/include/linux/netlink.h:5,
from ../include/tst_netlink.h:14,
from tst_crypto.c:13:
x86_64-buildroot-linux-musl/sysroot/usr/include/linux/sysinfo.h:8:8: error: redefinition of `struct sysinfo'
struct sysinfo {
^~~~~~~
In file included from ../include/tst_safe_macros.h:15,
from ../include/tst_test.h:93,
from tst_crypto.c:11:
x86_64-buildroot-linux-musl/sysroot/usr/include/sys/sysinfo.h:10:8: note: originally defined hereLink: https://lkml.kernel.org/r/20201015190013.8901-1-petr.vorel@gmail.com
Signed-off-by: Petr Vorel
Suggested-by: Rich Felker
Acked-by: Rich Felker
Cc: Peter Korsgaard
Cc: Baruch Siach
Cc: Florian Weimer
Signed-off-by: Andrew Morton
Signed-off-by: Linus Torvalds
Signed-off-by: Greg Kroah-Hartman
04 Jan, 2021
3 commits
-
This is the 5.10.4 stable release
* tag 'v5.10.4': (717 commits)
Linux 5.10.4
x86/CPU/AMD: Save AMD NodeId as cpu_die_id
drm/edid: fix objtool warning in drm_cvt_modes()
...Signed-off-by: Jason Liu
Conflicts:
drivers/gpu/drm/imx/dcss/dcss-plane.c
drivers/media/i2c/ov5640.c -
This is the 5.10.3 stable release
* tag 'v5.10.3': (41 commits)
Linux 5.10.3
md: fix a warning caused by a race between concurrent md_ioctl()s
nl80211: validate key indexes for cfg80211_registered_device
...Signed-off-by: Jason Liu
-
This is the 5.10.2 stable release
* tag 'v5.10.2': (17 commits)
Linux 5.10.2
serial: 8250_omap: Avoid FIFO corruption caused by MDR1 access
ALSA: pcm: oss: Fix potential out-of-bounds shift
...Signed-off-by: Jason Liu
Conflicts:
drivers/usb/host/xhci-hub.c
drivers/usb/host/xhci.h
30 Dec, 2020
2 commits
-
commit 0f966cba95c78029f491b433ea95ff38f414a761 upstream.
Add a per-transaction flag to indicate that the buffer
must be cleared when the transaction is complete to
prevent copies of sensitive data from being preserved
in memory.Signed-off-by: Todd Kjos
Link: https://lore.kernel.org/r/20201120233743.3617529-1-tkjos@google.com
Cc: stable
Signed-off-by: Greg Kroah-Hartman -
[ Upstream commit 75f4d4544db9fa34e1f04174f27d9f8a387be37d ]
The BIT() macro is not available for the UAPI headers. Moreover, it can
be defined differently in user space headers. Thus, replace its usage
with the _BITUL() macro which is already used in other macro definitions
in .Fixes: dc64cc7c6310 ("devlink: Add devlink reload limit option")
Signed-off-by: Tobias Klauser
Link: https://lore.kernel.org/r/20201215102531.16958-1-tklauser@distanz.ch
Signed-off-by: Jakub Kicinski
Signed-off-by: Sasha Levin
26 Dec, 2020
2 commits
-
commit 92eb6c3060ebe3adf381fd9899451c5b047bb14d upstream.
Commit 3f69cc60768b ("crypto: af_alg - Allow arbitrarily long algorithm
names") made the kernel start accepting arbitrarily long algorithm names
in sockaddr_alg. However, the actual length of the salg_name field
stayed at the original 64 bytes.This is broken because the kernel can access indices >= 64 in salg_name,
which is undefined behavior -- even though the memory that is accessed
is still located within the sockaddr structure. It would only be
defined behavior if the array were properly marked as arbitrary-length
(either by making it a flexible array, which is the recommended way
these days, or by making it an array of length 0 or 1).We can't simply change salg_name into a flexible array, since that would
break source compatibility with userspace programs that embed
sockaddr_alg into another struct, or (more commonly) declare a
sockaddr_alg like 'struct sockaddr_alg sa = { .salg_name = "foo" };'.One solution would be to change salg_name into a flexible array only
when '#ifdef __KERNEL__'. However, that would keep userspace without an
easy way to actually use the longer algorithm names.Instead, add a new structure 'sockaddr_alg_new' that has the flexible
array field, and expose it to both userspace and the kernel.
Make the kernel use it correctly in alg_bind().This addresses the syzbot report
"UBSAN: array-index-out-of-bounds in alg_bind"
(https://syzkaller.appspot.com/bug?extid=92ead4eb8e26a26d465e).Reported-by: syzbot+92ead4eb8e26a26d465e@syzkaller.appspotmail.com
Fixes: 3f69cc60768b ("crypto: af_alg - Allow arbitrarily long algorithm names")
Cc: # v4.12+
Signed-off-by: Eric Biggers
Signed-off-by: Herbert Xu
Signed-off-by: Greg Kroah-Hartman -
commit 3ceb6543e9cf6ed87cc1fbc6f23ca2db903564cd upstream.
There isn't really any valid reason to use __FSCRYPT_MODE_MAX or
FSCRYPT_POLICY_FLAGS_VALID in a userspace program. These constants are
only meant to be used by the kernel internally, and they are defined in
the UAPI header next to the mode numbers and flags only so that kernel
developers don't forget to update them when adding new modes or flags.In https://lkml.kernel.org/r/20201005074133.1958633-2-satyat@google.com
there was an example of someone wanting to use __FSCRYPT_MODE_MAX in a
user program, and it was wrong because the program would have broken if
__FSCRYPT_MODE_MAX were ever increased. So having this definition
available is harmful. FSCRYPT_POLICY_FLAGS_VALID has the same problem.So, remove these definitions from the UAPI header. Replace
FSCRYPT_POLICY_FLAGS_VALID with just listing the valid flags explicitly
in the one kernel function that needs it. Move __FSCRYPT_MODE_MAX to
fscrypt_private.h, remove the double underscores (which were only
present to discourage use by userspace), and add a BUILD_BUG_ON() and
comments to (hopefully) ensure it is kept in sync.Keep the old name FS_POLICY_FLAGS_VALID, since it's been around for
longer and there's a greater chance that removing it would break source
compatibility with some program. Indeed, mtd-utils is using it in
an #ifdef, and removing it would introduce compiler warnings (about
FS_POLICY_FLAGS_PAD_* being redefined) into the mtd-utils build.
However, reduce its value to 0x07 so that it only includes the flags
with old names (the ones present before Linux 5.4), and try to make it
clear that it's now "frozen" and no new flags should be added to it.Fixes: 2336d0deb2d4 ("fscrypt: use FSCRYPT_ prefix for uapi constants")
Cc: # v5.4+
Link: https://lore.kernel.org/r/20201024005132.495952-1-ebiggers@kernel.org
Signed-off-by: Eric Biggers
Signed-off-by: Greg Kroah-Hartman
21 Dec, 2020
1 commit
-
commit 0032ce0f85a269a006e91277be5fdbc05fad8426 upstream.
ptrace_get_syscall_info() is potentially copying uninitialized stack
memory to userspace, since the compiler may leave a 3-byte hole near the
beginning of `info`. Fix it by adding a padding field to `struct
ptrace_syscall_info`.Fixes: 201766a20e30 ("ptrace: add PTRACE_GET_SYSCALL_INFO request")
Suggested-by: Dan Carpenter
Signed-off-by: Peilin Ye
Reviewed-by: Dmitry V. Levin
Cc: stable@vger.kernel.org
Link: https://lore.kernel.org/r/20200801152044.230416-1-yepeilin.cs@gmail.com
Signed-off-by: Christian Brauner
Signed-off-by: Greg Kroah-Hartman
18 Dec, 2020
15 commits
-
* sensor/next: (31 commits)
input: rpmsg-input: convert pm_qos_*() usage to new cpu_latency_qos_*()
LF-665-4 input: mma8450: fix build break
LF-375 sensor: fxls8471: set output data rate when device init
LF-99 hwmon: mag3110: correct processing order after probe error
MLK-22296-4 misc: mpl3115: Fix build warning when CONFIG_PM_SLEEP=n
... -
* net/next: (207 commits)
LF-2788-2 net: ethernet: dwmac-imx: delete check for platform w/o SCU FW
tsn: status return variable initialize to be 0
net:tsn: fix coverity issues
net: tsn: fix headfile voliates the new rule
net:tsn: netlink interface for APP layer to config TSN capability hardware ports
... -
* mxc/next: (279 commits)
LF-2111-2: mxc: vpu_windsor: Avoid hide parameter
MLK-24960: [8QM_MEK/8QXP_MEK]mxc:vpu_malone: move timestamp manager to firmware
MLK-24959: [8QM_MEK/8QXP_MEK]mxc:vpu_windsor: move timestamp handler to firmware
MLK-24906: [8QM_MEK/8QXP_MEK]mxc:vpu_malone: report V4L2_COLORSPACE_DEFAULT before seq hdr found
MLK-24593:[8QM_MEK/8QXP_MEK]mxc:vpu_windsor: support change bitrate dynamically
... -
* misc/next: (8 commits)
LF-2567-5 dma-buf: inlcude new headfile linux/dma-map-ops.h
MGS-5565-1 staging: android: ion: Flush outer cache after zero CMA allocated memory
MGS-5565 staging: android: ion: Flush cache after zero CMA allocated memory
Documentation: mfd: Add DT bindings for i.MX Mix
mfd: Add i.MX generic mix support
... -
* display/next: (467 commits)
MMFMWK-8917-2: drm/imx/dcss: add extra plane check
MMFMWK-8917-1: drm/imx/dcss: remove unnecessary warning
LF-3024: drm/imx/dcss: allow primary plane to be less than crtc size
MLK-24081-06: drm: bridge: imx: Add opcode for hdmi rx driver
MLK-24081-03: drm: bridge: cdns-cec: support hdmi rx cec
... -
* crypto/next: (39 commits)
MLK-23746 crypto: dcp - add power management support
crypto: dcp - check zero-length input
MLK-24912-2 crypto: caam - fix RNG vs. hwrng kthread race
MLK-24912-1 crypto: caam/jr - update jr_list during suspend/resume
LF-2943 crypto: caam - optimize RNG sample size
... -
* capture/next: (165 commits)
LF-2976 media: adv7180: fix not work by "ERROR: v4l2 capture: slave not found!"
MLK-24081: hdmirx: fix build error in LF branch
MLK-24081-06: staging: media: imx: Add hdmi rx driver
MLK-24081-04: staging: media: imx_csi: support hdmi rx for imx8qm
MLK-24081-04: staging: media: imx_csi: support hdmi rx for imx8qm
... -
* origin/net/tsn:
tsn: status return variable initialize to be 0
net:tsn: fix coverity issues
net: tsn: fix headfile voliates the new rule
net:tsn: netlink interface for APP layer to config TSN capability hardware ports -
* origin/net/dpaa2: (31 commits)
bus: fsl-mc: added missing fields to dprc_rsp_get_obj_region structure
bus: fsl-mc: simplify DPRC version check
Fixed qbman alignment error in the virtualization context
dpaa2-mac: select FSL_XGMAC_MDIO
dpaa2-mac: probe standalone DPMAC objects
... -
* origin/mxc/vpu: (123 commits)
LF-2111-2: mxc: vpu_windsor: Avoid hide parameter
MLK-24960: [8QM_MEK/8QXP_MEK]mxc:vpu_malone: move timestamp manager to firmware
MLK-24959: [8QM_MEK/8QXP_MEK]mxc:vpu_windsor: move timestamp handler to firmware
MLK-24906: [8QM_MEK/8QXP_MEK]mxc:vpu_malone: report V4L2_COLORSPACE_DEFAULT before seq hdr found
MLK-24593:[8QM_MEK/8QXP_MEK]mxc:vpu_windsor: support change bitrate dynamically
... -
* origin/mxc/sim: (33 commits)
LF-2932 mxc: sim/emvsim: fix competition when call pm_runtime_put
MLK-24363-2 mxc: emvsim: fix error report in probe stage
MLK-24363-1 mxc: emvsim: add error check when enable clk
MLK-24364 mxc: sim: add runtime pm support
LF-1762-7 mxc: sim: replace '---help---' in Kconfig files with 'help'
... -
* origin/display/fbdev: (40 commits)
LF-2723-2 video: epdc: fix kernel dump issue
LF-2723-1 video: epdc_v2: fix kernel dump issue
LF-2658 video: fbdev: mxc: Forward ipuv3 LCD external port(mxc_lcdif) driver from imx_4.19.y kernel
LF-2225-3 fbdev: mxc_ipuv3_fb: drop the using of FBINFO_MISC_USEREVENT
LF-2225-2 fbdev: mxc_hdmi: drop the using of FBINFO_MISC_USEREVENT
... -
* origin/display/drm: (9 commits)
LF-1189-1 media: bus format: Add RGB565_1X30_PADLO support
drm/fourcc: add a 10bits fully packed variant of NV12
drm/fourcc: add modifier for vivante compressed tiled layout
MLK-17368-1 drm: add fourcc codes for Verisilicon tiled formats
MLK-16290 drm: Add drm_of_component_probe_with_match() helper
... -
* origin/capture/mxc: (23 commits)
LF-2976 media: adv7180: fix not work by "ERROR: v4l2 capture: slave not found!"
Revert "LF-2488 media: mxc V4L2 capture: fix coverity issue 11024996 & 11024997"
LF-2488 media: mxc V4L2 capture: fix coverity issue 11024996 & 11024997
LF-2483 media: mxc V4L2 capture: fix coverity issue 10953010
LF-2229-2 media: csi: Fix the kernel dump issue for VTE testing
... -
* origin/audio/dsp: (117 commits)
MLK-24929 ASoC: fsl_dsp: Support aac streams for cplay
MLK-24924-2 dsp: 8mp: change ocram layout for lpa
MLK-24883 ASoC: fsl_dsp: Add sections check for dsp firmware
MLK-24816-2 ASoc: fsl_dsp: Correct set connected component port
MLK-24816-1 ASoc: fsl_dsp: Support seek for compress pipeline
...
14 Dec, 2020
12 commits
-
After commit
622445541b75 ("kbuild: detect missing "WITH Linux-syscall-note" for uapi headers")
the headfile must explicitly include "WITH Linux-syscall-note".Signed-off-by: Dong Aisheng
-
This patch provids netlink method to configure the TSN protocols hardwares.
TSN guaranteed packet transport with bounded low latency, low packet delay
variation, and low packet loss by hardware and software methods.The three basic components of TSN are:
1. Time synchronization: This was implement by 8021AS which base on the
IEEE1588 precision Time Protocol. This is configured by the other way
in kernel.
8021AS not included in this patch.2. Scheduling and traffic shaping and per-stream filter policing:
This patch support Qbv/Qci/Qbu/8021CB/Qav etc.3. Selection of communication paths:
This patch not support the pure software only TSN protocols(like Qcc)
but hardware related configuration.TSN Protocols supports by this patch: Qbv/Qci/Qbu/Credit-base Shaper(Qav).
This patch verified on NXP ls1028ardb board.Signed-off-by: Po Liu
-
This patch is to fix CONFIG_COMPAT leak during headers installing
by replacing CONFIG_COMPAT kernel option with FM_COMPAT instead.Signed-off-by: Yangbo Lu
-
Signed-off-by: Madalin Bucur
-
This patch adds the Kernel support for the caam-keygen user-space
application. It has two IOCTL calls for key and blob generation and
import a black key from a blob.This support is included in CRYPTO_DEV_FSL_CAAM_TK_API (tagged key
support).Signed-off-by: Iuliana Prodan
Reviewed-by: Horia Geantă
(cherry picked from commit 60baeafa838f98a5ab1069716b8e41d28e155137)Squashed fixes:
dd746ff04645 ("MLK-24496 crypto: caam - add tag object header to blob")
b8c49eddfd68 ("MLK-24517-3 crypto: caam - add null terminator to temporary buffer")
d7c41169bc8e ("MLK-24517-4 crypto: caam - validate arguments received from user-space")Signed-off-by: Iuliana Prodan
Reviewed-by: Horia Geantă -
Signed-off-by: Dong Aisheng
-
Adding userspace support for the MC (Management Complex) means exporting
an ioctl capable device file representing the root resource container.This new functionality in the fsl-mc bus driver intends to provide
userspace applications an interface to interact with the MC firmware.Commands that are composed in userspace are sent to the MC firmware
through the FSL_MC_SEND_MC_COMMAND ioctl. By default the implicit MC
I/O portal is used for this operation, but if the implicit one is busy,
a dynamic portal is allocated and then freed upon execution.Signed-off-by: Ioana Ciornei
-
Define "struct fsl_mc_command" as a structure that can cross the
user/kernel boundary.Signed-off-by: Ioana Ciornei
-
ISO have defined some color primaries/transfer/matrix,
but not defined in v4l2 framework,
so add some definitionSigned-off-by: Ming Qian
Reviewed-by: Shijie Qin -
Copied from 4.14.78 GA.
Module onwer could merge it when adding drivers code.Signed-off-by: Dong Aisheng
-
Add hantro decoder driver:
drivers/mxc/hantro
include/linux/hantrodec.h
include/uapi/linux/hantrodec.hSigned-off-by: Zhou Peng
-
Copied from 4.14.78 GA.
Module onwer could merge it when adding drivers code.Signed-off-by: Dong Aisheng
