* [PATCH 4.19 1/2] cgroup-v1: Require capabilities to set release_agent
2022-02-09 19:14 [PATCH 4.19 0/2] 4.19.229-rc1 review Greg Kroah-Hartman
@ 2022-02-09 19:14 ` Greg Kroah-Hartman
2022-02-09 19:14 ` [PATCH 4.19 2/2] moxart: fix potential use-after-free on remove path Greg Kroah-Hartman
` (8 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Greg Kroah-Hartman @ 2022-02-09 19:14 UTC (permalink / raw)
To: linux-kernel
Cc: Greg Kroah-Hartman, stable, Tabitha Sable, Eric W. Biederman,
Tejun Heo, Michal Koutný
From: Eric W. Biederman <ebiederm@xmission.com>
commit 24f6008564183aa120d07c03d9289519c2fe02af upstream.
The cgroup release_agent is called with call_usermodehelper. The function
call_usermodehelper starts the release_agent with a full set fo capabilities.
Therefore require capabilities when setting the release_agaent.
Reported-by: Tabitha Sable <tabitha.c.sable@gmail.com>
Tested-by: Tabitha Sable <tabitha.c.sable@gmail.com>
Fixes: 81a6a5cdd2c5 ("Task Control Groups: automatic userspace notification of idle cgroups")
Cc: stable@vger.kernel.org # v2.6.24+
Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
Signed-off-by: Tejun Heo <tj@kernel.org>
[mkoutny: Adjust for pre-fs_context, duplicate mount/remount check, drop log messages.]
Acked-by: Michal Koutný <mkoutny@suse.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
kernel/cgroup/cgroup-v1.c | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
--- a/kernel/cgroup/cgroup-v1.c
+++ b/kernel/cgroup/cgroup-v1.c
@@ -577,6 +577,14 @@ static ssize_t cgroup_release_agent_writ
BUILD_BUG_ON(sizeof(cgrp->root->release_agent_path) < PATH_MAX);
+ /*
+ * Release agent gets called with all capabilities,
+ * require capabilities to set release agent.
+ */
+ if ((of->file->f_cred->user_ns != &init_user_ns) ||
+ !capable(CAP_SYS_ADMIN))
+ return -EPERM;
+
cgrp = cgroup_kn_lock_live(of->kn, false);
if (!cgrp)
return -ENODEV;
@@ -1048,6 +1056,7 @@ static int cgroup1_remount(struct kernfs
{
int ret = 0;
struct cgroup_root *root = cgroup_root_from_kf(kf_root);
+ struct cgroup_namespace *ns = current->nsproxy->cgroup_ns;
struct cgroup_sb_opts opts;
u16 added_mask, removed_mask;
@@ -1061,6 +1070,12 @@ static int cgroup1_remount(struct kernfs
if (opts.subsys_mask != root->subsys_mask || opts.release_agent)
pr_warn("option changes via remount are deprecated (pid=%d comm=%s)\n",
task_tgid_nr(current), current->comm);
+ /* See cgroup1_mount release_agent handling */
+ if (opts.release_agent &&
+ ((ns->user_ns != &init_user_ns) || !capable(CAP_SYS_ADMIN))) {
+ ret = -EINVAL;
+ goto out_unlock;
+ }
added_mask = opts.subsys_mask & ~root->subsys_mask;
removed_mask = root->subsys_mask & ~opts.subsys_mask;
@@ -1224,6 +1239,15 @@ struct dentry *cgroup1_mount(struct file
ret = -EPERM;
goto out_unlock;
}
+ /*
+ * Release agent gets called with all capabilities,
+ * require capabilities to set release agent.
+ */
+ if (opts.release_agent &&
+ ((ns->user_ns != &init_user_ns) || !capable(CAP_SYS_ADMIN))) {
+ ret = -EINVAL;
+ goto out_unlock;
+ }
root = kzalloc(sizeof(*root), GFP_KERNEL);
if (!root) {
^ permalink raw reply [flat|nested] 11+ messages in thread* [PATCH 4.19 2/2] moxart: fix potential use-after-free on remove path
2022-02-09 19:14 [PATCH 4.19 0/2] 4.19.229-rc1 review Greg Kroah-Hartman
2022-02-09 19:14 ` [PATCH 4.19 1/2] cgroup-v1: Require capabilities to set release_agent Greg Kroah-Hartman
@ 2022-02-09 19:14 ` Greg Kroah-Hartman
2022-02-09 21:29 ` [PATCH 4.19 0/2] 4.19.229-rc1 review Pavel Machek
` (7 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Greg Kroah-Hartman @ 2022-02-09 19:14 UTC (permalink / raw)
To: linux-kernel
Cc: Greg Kroah-Hartman, stable, Ulf Hansson, Xiyu Yang, Xin Xiong,
Xin Tan, Tony Lindgren, Yang Li, linux-mmc, whitehat002
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
commit bd2db32e7c3e35bd4d9b8bbff689434a50893546 upstream.
It was reported that the mmc host structure could be accessed after it
was freed in moxart_remove(), so fix this by saving the base register of
the device and using it instead of the pointer dereference.
Cc: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Xiyu Yang <xiyuyang19@fudan.edu.cn>
Cc: Xin Xiong <xiongx18@fudan.edu.cn>
Cc: Xin Tan <tanxin.ctf@gmail.com>
Cc: Tony Lindgren <tony@atomide.com>
Cc: Yang Li <yang.lee@linux.alibaba.com>
Cc: linux-mmc@vger.kernel.org
Cc: stable <stable@vger.kernel.org>
Reported-by: whitehat002 <hackyzh002@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Link: https://lore.kernel.org/r/20220127071638.4057899-1-gregkh@linuxfoundation.org
Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
drivers/mmc/host/moxart-mmc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/drivers/mmc/host/moxart-mmc.c
+++ b/drivers/mmc/host/moxart-mmc.c
@@ -696,12 +696,12 @@ static int moxart_remove(struct platform
if (!IS_ERR(host->dma_chan_rx))
dma_release_channel(host->dma_chan_rx);
mmc_remove_host(mmc);
- mmc_free_host(mmc);
writel(0, host->base + REG_INTERRUPT_MASK);
writel(0, host->base + REG_POWER_CONTROL);
writel(readl(host->base + REG_CLOCK_CONTROL) | CLK_OFF,
host->base + REG_CLOCK_CONTROL);
+ mmc_free_host(mmc);
}
return 0;
}
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: [PATCH 4.19 0/2] 4.19.229-rc1 review
2022-02-09 19:14 [PATCH 4.19 0/2] 4.19.229-rc1 review Greg Kroah-Hartman
2022-02-09 19:14 ` [PATCH 4.19 1/2] cgroup-v1: Require capabilities to set release_agent Greg Kroah-Hartman
2022-02-09 19:14 ` [PATCH 4.19 2/2] moxart: fix potential use-after-free on remove path Greg Kroah-Hartman
@ 2022-02-09 21:29 ` Pavel Machek
2022-02-10 0:59 ` Shuah Khan
` (6 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Pavel Machek @ 2022-02-09 21:29 UTC (permalink / raw)
To: Greg Kroah-Hartman
Cc: linux-kernel, stable, torvalds, akpm, linux, shuah, patches,
lkft-triage, pavel, jonathanh, f.fainelli, sudipm.mukherjee,
slade
[-- Attachment #1: Type: text/plain, Size: 660 bytes --]
Hi!
> This is the start of the stable review cycle for the 4.19.229 release.
> There are 2 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
CIP testing did not find any problems here:
https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/tree/linux-4.19.y
Tested-by: Pavel Machek (CIP) <pavel@denx.de>
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: [PATCH 4.19 0/2] 4.19.229-rc1 review
2022-02-09 19:14 [PATCH 4.19 0/2] 4.19.229-rc1 review Greg Kroah-Hartman
` (2 preceding siblings ...)
2022-02-09 21:29 ` [PATCH 4.19 0/2] 4.19.229-rc1 review Pavel Machek
@ 2022-02-10 0:59 ` Shuah Khan
2022-02-10 8:33 ` Jon Hunter
` (5 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Shuah Khan @ 2022-02-10 0:59 UTC (permalink / raw)
To: Greg Kroah-Hartman, linux-kernel
Cc: stable, torvalds, akpm, linux, shuah, patches, lkft-triage, pavel,
jonathanh, f.fainelli, sudipm.mukherjee, slade, Shuah Khan
On 2/9/22 12:14 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.19.229 release.
> There are 2 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Fri, 11 Feb 2022 19:12:41 +0000.
> Anything received after that time might be too late.
>
> The whole patch series can be found in one patch at:
> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.19.229-rc1.gz
> or in the git tree and branch at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.19.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
>
Compiled and booted on my test system. No dmesg regressions.
Tested-by: Shuah Khan <skhan@linuxfoundation.org>
thanks,
-- Shuah
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: [PATCH 4.19 0/2] 4.19.229-rc1 review
2022-02-09 19:14 [PATCH 4.19 0/2] 4.19.229-rc1 review Greg Kroah-Hartman
` (3 preceding siblings ...)
2022-02-10 0:59 ` Shuah Khan
@ 2022-02-10 8:33 ` Jon Hunter
2022-02-10 16:05 ` Sudip Mukherjee
` (4 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Jon Hunter @ 2022-02-10 8:33 UTC (permalink / raw)
To: Greg Kroah-Hartman
Cc: Greg Kroah-Hartman, stable, torvalds, akpm, linux, shuah, patches,
lkft-triage, pavel, jonathanh, f.fainelli, sudipm.mukherjee,
slade, linux-tegra
On Wed, 09 Feb 2022 20:14:02 +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.19.229 release.
> There are 2 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Fri, 11 Feb 2022 19:12:41 +0000.
> Anything received after that time might be too late.
>
> The whole patch series can be found in one patch at:
> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.19.229-rc1.gz
> or in the git tree and branch at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.19.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
All tests passing for Tegra ...
Test results for stable-v4.19:
10 builds: 10 pass, 0 fail
22 boots: 22 pass, 0 fail
40 tests: 40 pass, 0 fail
Linux version: 4.19.229-rc1-g020dc380ec76
Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000,
tegra194-p2972-0000, tegra20-ventana,
tegra210-p2371-2180, tegra30-cardhu-a04
Tested-by: Jon Hunter <jonathanh@nvidia.com>
Jon
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: [PATCH 4.19 0/2] 4.19.229-rc1 review
2022-02-09 19:14 [PATCH 4.19 0/2] 4.19.229-rc1 review Greg Kroah-Hartman
` (4 preceding siblings ...)
2022-02-10 8:33 ` Jon Hunter
@ 2022-02-10 16:05 ` Sudip Mukherjee
2022-02-10 17:18 ` Naresh Kamboju
` (3 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Sudip Mukherjee @ 2022-02-10 16:05 UTC (permalink / raw)
To: Greg Kroah-Hartman
Cc: linux-kernel, stable, torvalds, akpm, linux, shuah, patches,
lkft-triage, pavel, jonathanh, f.fainelli, slade
Hi Greg,
On Wed, Feb 09, 2022 at 08:14:02PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.19.229 release.
> There are 2 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Fri, 11 Feb 2022 19:12:41 +0000.
> Anything received after that time might be too late.
Build test:
mips (gcc version 11.2.1 20220121): 63 configs -> no failure
arm (gcc version 11.2.1 20220121): 116 configs -> no new failure
arm64 (gcc version 11.2.1 20220121): 2 configs -> no failure
x86_64 (gcc version 11.2.1 20220121): 4 configs -> no failure
Boot test:
x86_64: Booted on my test laptop. No regression.
x86_64: Booted on qemu. No regression. [1]
[1]. https://openqa.qa.codethink.co.uk/tests/736
Tested-by: Sudip Mukherjee <sudip.mukherjee@codethink.co.uk>
--
Regards
Sudip
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: [PATCH 4.19 0/2] 4.19.229-rc1 review
2022-02-09 19:14 [PATCH 4.19 0/2] 4.19.229-rc1 review Greg Kroah-Hartman
` (5 preceding siblings ...)
2022-02-10 16:05 ` Sudip Mukherjee
@ 2022-02-10 17:18 ` Naresh Kamboju
2022-02-10 18:11 ` Jeffrin Thalakkottoor
` (2 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Naresh Kamboju @ 2022-02-10 17:18 UTC (permalink / raw)
To: Greg Kroah-Hartman
Cc: linux-kernel, stable, torvalds, akpm, linux, shuah, patches,
lkft-triage, pavel, jonathanh, f.fainelli, sudipm.mukherjee,
slade
On Thu, 10 Feb 2022 at 00:45, Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
>
> This is the start of the stable review cycle for the 4.19.229 release.
> There are 2 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Fri, 11 Feb 2022 19:12:41 +0000.
> Anything received after that time might be too late.
>
> The whole patch series can be found in one patch at:
> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.19.229-rc1.gz
> or in the git tree and branch at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.19.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
Results from Linaro’s test farm.
No regressions on arm64, arm, x86_64, and i386.
Tested-by: Linux Kernel Functional Testing <lkft@linaro.org>
## Build
* kernel: 4.19.229-rc1
* git: https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc
* git branch: linux-4.19.y
* git commit: 020dc380ec76524a264536664d516a5a4d7cd45d
* git describe: v4.19.227-90-g020dc380ec76
* test details:
https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-4.19.y/build/v4.19.227-90-g020dc380ec76
## Test Regressions (compared to v4.19.227-87-gb06b07466af8)
No test regressions found.
## Metric Regressions (compared to v4.19.227-87-gb06b07466af8)
No metric regressions found.
## Test Fixes (compared to v4.19.227-87-gb06b07466af8)
No test fixes found.
## Metric Fixes (compared to v4.19.227-87-gb06b07466af8)
No metric fixes found.
## Test result summary
total: 61877, pass: 52177, fail: 270, skip: 8370, xfail: 1060
## Build Summary
* arm: 130 total, 130 passed, 0 failed
* arm64: 35 total, 35 passed, 0 failed
* i386: 18 total, 18 passed, 0 failed
* mips: 26 total, 26 passed, 0 failed
* powerpc: 52 total, 39 passed, 13 failed
* s390: 12 total, 12 passed, 0 failed
* sparc: 12 total, 12 passed, 0 failed
* x86_64: 34 total, 34 passed, 0 failed
## Test suites summary
* fwts
* igt-gpu-tools
* kselftest-android
* kselftest-arm64
* kselftest-arm64/arm64.btitest.bti_c_func
* kselftest-arm64/arm64.btitest.bti_j_func
* kselftest-arm64/arm64.btitest.bti_jc_func
* kselftest-arm64/arm64.btitest.bti_none_func
* kselftest-arm64/arm64.btitest.nohint_func
* kselftest-arm64/arm64.btitest.paciasp_func
* kselftest-arm64/arm64.nobtitest.bti_c_func
* kselftest-arm64/arm64.nobtitest.bti_j_func
* kselftest-arm64/arm64.nobtitest.bti_jc_func
* kselftest-arm64/arm64.nobtitest.bti_none_func
* kselftest-arm64/arm64.nobtitest.nohint_func
* kselftest-arm64/arm64.nobtitest.paciasp_func
* kselftest-breakpoints
* kselftest-capabilities
* kselftest-cgroup
* kselftest-clone3
* kselftest-core
* kselftest-cpu-hotplug
* kselftest-cpufreq
* kselftest-drivers
* kselftest-efivarfs
* kselftest-filesystems
* kselftest-firmware
* kselftest-fpu
* kselftest-futex
* kselftest-gpio
* kselftest-intel_pstate
* kselftest-ipc
* kselftest-ir
* kselftest-kcmp
* kselftest-kvm
* kselftest-lib
* kselftest-livepatch
* kselftest-membarrier
* kselftest-net
* kselftest-openat2
* kselftest-pid_namespace
* kselftest-pidfd
* kselftest-proc
* kselftest-pstore
* kselftest-ptrace
* kselftest-rseq
* kselftest-rtc
* kselftest-seccomp
* kselftest-sigaltstack
* kselftest-size
* kselftest-splice
* kselftest-static_keys
* kselftest-sync
* kselftest-sysctl
* kselftest-timens
* kselftest-timers
* kselftest-tmpfs
* kselftest-tpm2
* kselftest-user
* kselftest-vm
* kselftest-x86
* kselftest-zram
* kvm-unit-tests
* libhugetlbfs
* linux-log-parser
* ltp-cap_bounds-tests
* ltp-commands-tests
* ltp-containers-tests
* ltp-controllers-tests
* ltp-cpuhotplug-tests
* ltp-crypto-tests
* ltp-cve-tests
* ltp-dio-tests
* ltp-fcntl-locktests-tests
* ltp-filecaps-tests
* ltp-fs-tests
* ltp-fs_bind-tests
* ltp-fs_perms_simple-tests
* ltp-fsx-tests
* ltp-hugetlb-tests
* ltp-io-tests
* ltp-ipc-tests
* ltp-math-tests
* ltp-mm-tests
* ltp-nptl-tests
* ltp-open-posix-tests
* ltp-pty-tests
* ltp-sched-tests
* ltp-securebits-tests
* ltp-syscalls-tests
* ltp-tracing-tests
* network-basic-tests
* packetdrill
* rcutorture
* ssuite
* v4l2-compliance
--
Linaro LKFT
https://lkft.linaro.org
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: [PATCH 4.19 0/2] 4.19.229-rc1 review
2022-02-09 19:14 [PATCH 4.19 0/2] 4.19.229-rc1 review Greg Kroah-Hartman
` (6 preceding siblings ...)
2022-02-10 17:18 ` Naresh Kamboju
@ 2022-02-10 18:11 ` Jeffrin Thalakkottoor
2022-02-10 21:00 ` Guenter Roeck
2022-02-11 0:59 ` Samuel Zou
9 siblings, 0 replies; 11+ messages in thread
From: Jeffrin Thalakkottoor @ 2022-02-10 18:11 UTC (permalink / raw)
To: Greg Kroah-Hartman
Cc: lkml, stable, torvalds, Andrew Morton, Guenter Roeck, Shuah Khan,
patches, lkft-triage, Pavel Machek, jonathanh, f.fainelli,
sudipm.mukherjee, slade
[-- Attachment #1: Type: text/plain, Size: 1581 bytes --]
On Wed, Feb 9, 2022 at 2:25 PM Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
>
> This is the start of the stable review cycle for the 4.19.229 release.
> There are 2 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Fri, 11 Feb 2022 19:12:41 +0000.
> Anything received after that time might be too late.
>
> The whole patch series can be found in one patch at:
> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.19.229-rc1.gz
> or in the git tree and branch at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.19.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
hello,
Compiled and booted kernel 4.19.229-rc1+ on :
Processor Information:
Socket Designation: FM2
Type: Central Processor
Family: A-Series
Manufacturer: AuthenticAMD
ID: 31 0F 61 00 FF FB 8B 17
Signature: Family 21, Model 19, Stepping 1
i have a new display card of nvidia chipset. iam using non-free drivers here.
01:00.0 VGA compatible controller: NVIDIA Corporation GP108 [GeForce
GT 1030] (rev a1) (from lspci output)
resources: irq:29 memory:fd000000-fdffffff memory:c0000000-cfffffff
memory:d0000000-d1ffffff ioport:e000(size=128) memory:c0000-dffff
(from "sudo lshw -c video" output)
dmesg related actions attached.
Tested-by: Jeffrin Jose T <jeffrin@rajagiritech.edu.in>
--
software engineer
rajagiri school of engineering and technology - autonomous
[-- Attachment #2: dmesg0.txt --]
[-- Type: text/plain, Size: 1061 bytes --]
$sudo sysctl -w kernel.dmesg_restrict=0
kernel.dmesg_restrict = 0
$dmesg -l emerg
$dmesg -l alert
$dmesg -l crit
$dmesg -l err
[ 1.270092] nvidiafb: unknown NV_ARCH
[ 5.531992] cgroup: cgroup2: unknown option "memory_recursiveprot"
$dmesg -l warn
[ 0.017384] ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has valid Length but zero Address: 0x0000000000000000/0x1 (20180810/tbfadt-615)
[ 1.270040] nvidiafb_setup START
[ 1.270047] nvidiafb_probe START
[ 12.329696] nvidia: loading out-of-tree module taints kernel.
[ 12.329710] nvidia: module license 'NVIDIA' taints kernel.
[ 12.329711] Disabling lock debugging due to kernel taint
[ 12.486289] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 470.103.01 Thu Jan 6 12:10:04 UTC 2022
[ 31.547073] resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000dffff window]
[ 31.547483] caller _nv000722rm+0x1ad/0x200 [nvidia] mapping multiple BARs
[ 40.099402] kauditd_printk_skb: 11 callbacks suppressed
$
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: [PATCH 4.19 0/2] 4.19.229-rc1 review
2022-02-09 19:14 [PATCH 4.19 0/2] 4.19.229-rc1 review Greg Kroah-Hartman
` (7 preceding siblings ...)
2022-02-10 18:11 ` Jeffrin Thalakkottoor
@ 2022-02-10 21:00 ` Guenter Roeck
2022-02-11 0:59 ` Samuel Zou
9 siblings, 0 replies; 11+ messages in thread
From: Guenter Roeck @ 2022-02-10 21:00 UTC (permalink / raw)
To: Greg Kroah-Hartman
Cc: linux-kernel, stable, torvalds, akpm, shuah, patches, lkft-triage,
pavel, jonathanh, f.fainelli, sudipm.mukherjee, slade
On Wed, Feb 09, 2022 at 08:14:02PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.19.229 release.
> There are 2 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Fri, 11 Feb 2022 19:12:41 +0000.
> Anything received after that time might be too late.
>
Build results:
total: 156 pass: 156 fail: 0
Qemu test results:
total: 425 pass: 425 fail: 0
Tested-by: Guenter Roeck <linux@roeck-us.net>
Guenter
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: [PATCH 4.19 0/2] 4.19.229-rc1 review
2022-02-09 19:14 [PATCH 4.19 0/2] 4.19.229-rc1 review Greg Kroah-Hartman
` (8 preceding siblings ...)
2022-02-10 21:00 ` Guenter Roeck
@ 2022-02-11 0:59 ` Samuel Zou
9 siblings, 0 replies; 11+ messages in thread
From: Samuel Zou @ 2022-02-11 0:59 UTC (permalink / raw)
To: Greg Kroah-Hartman, linux-kernel
Cc: stable, torvalds, akpm, linux, shuah, patches, lkft-triage, pavel,
jonathanh, f.fainelli, sudipm.mukherjee, slade
On 2022/2/10 3:14, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.19.229 release.
> There are 2 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Fri, 11 Feb 2022 19:12:41 +0000.
> Anything received after that time might be too late.
>
> The whole patch series can be found in one patch at:
> https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.19.229-rc1.gz
> or in the git tree and branch at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.19.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
>
Tested on arm64 and x86 for 4.19.229-rc1,
Kernel repo:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Branch: linux-4.19.y
Version: 4.19.229-rc1
Commit: 020dc380ec76524a264536664d516a5a4d7cd45d
Compiler: gcc version 7.3.0 (GCC)
arm64:
--------------------------------------------------------------------
Testcase Result Summary:
total: 8938
passed: 8938
failed: 0
timeout: 0
--------------------------------------------------------------------
x86:
--------------------------------------------------------------------
Testcase Result Summary:
total: 8938
passed: 8938
failed: 0
timeout: 0
--------------------------------------------------------------------
Tested-by: Hulk Robot <hulkrobot@huawei.com>
^ permalink raw reply [flat|nested] 11+ messages in thread