This is the start of the stable review cycle for the 4.14.310 release.
There are 20 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 Sat, 18 Mar 2023 08:33:04 +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.14.310-rc2.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.14.y
and the diffstat can be found below.
thanks,
greg k-h
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <[email protected]>
Linux 4.14.310-rc2
Rhythm Mahajan <[email protected]>
x86/cpu: Fix LFENCE serialization check in init_amd()
John Harrison <[email protected]>
drm/i915: Don't use BAR mappings for ring buffers with LLC
Tung Nguyen <[email protected]>
tipc: improve function tipc_wait_for_cond()
Paul Elder <[email protected]>
media: ov5640: Fix analogue gain control
Alvaro Karsz <[email protected]>
PCI: Add SolidRun vendor ID
Nathan Chancellor <[email protected]>
macintosh: windfarm: Use unsigned type for 1-bit bitfields
Edward Humes <[email protected]>
alpha: fix R_ALPHA_LITERAL reloc for large modules
xurui <[email protected]>
MIPS: Fix a compilation issue
Dmitry Baryshkov <[email protected]>
clk: qcom: mmcc-apq8084: remove spdm clocks
Shigeru Yoshida <[email protected]>
net: caif: Fix use-after-free in cfusbl_device_notify()
Eric Dumazet <[email protected]>
ila: do not generate empty messages in ila_xlat_nl_cmd_get_mapping()
Kang Chen <[email protected]>
nfc: fdp: add null check of devm_kmalloc_array in fdp_nci_i2c_read_device_properties
Fedor Pchelkin <[email protected]>
nfc: change order inside nfc_se_io error path
Zhihao Cheng <[email protected]>
ext4: zero i_disksize when initializing the bootloader inode
Ye Bin <[email protected]>
ext4: fix WARNING in ext4_update_inline_data
Ye Bin <[email protected]>
ext4: move where set the MAY_INLINE_DATA flag is set
Darrick J. Wong <[email protected]>
ext4: fix another off-by-one fsmap error on 1k block filesystems
Eric Whitney <[email protected]>
ext4: fix RENAME_WHITEOUT handling for inline directories
Andrew Cooper <[email protected]>
x86/CPU/AMD: Disable XSAVES on AMD family 0x17
Theodore Ts'o <[email protected]>
fs: prevent out-of-bounds array speculation when closing a file descriptor
-------------
Diffstat:
Makefile | 4 +-
arch/alpha/kernel/module.c | 4 +-
arch/mips/include/asm/mach-rc32434/pci.h | 2 +-
arch/x86/kernel/cpu/amd.c | 11 +-
drivers/clk/qcom/mmcc-apq8084.c | 271 -------------------------------
drivers/gpu/drm/i915/intel_ringbuffer.c | 4 +-
drivers/macintosh/windfarm_lm75_sensor.c | 4 +-
drivers/macintosh/windfarm_smu_sensors.c | 4 +-
drivers/media/i2c/ov5640.c | 2 +-
drivers/nfc/fdp/i2c.c | 4 +
fs/ext4/fsmap.c | 2 +
fs/ext4/inline.c | 1 -
fs/ext4/inode.c | 7 +-
fs/ext4/ioctl.c | 1 +
fs/ext4/namei.c | 13 +-
fs/ext4/xattr.c | 3 +
fs/file.c | 1 +
include/linux/pci_ids.h | 2 +
net/caif/caif_usb.c | 3 +
net/ipv6/ila/ila_xlat.c | 1 +
net/nfc/netlink.c | 2 +-
net/tipc/socket.c | 2 +-
22 files changed, 53 insertions(+), 295 deletions(-)
Hi!
> This is the start of the stable review cycle for the 4.14.310 release.
> There are 20 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.
> Dmitry Baryshkov <[email protected]>
> clk: qcom: mmcc-apq8084: remove spdm clocks
This looks like a cleanup, we should not need it in stable.
> Paul Elder <[email protected]>
> media: ov5640: Fix analogue gain control
This is an API tweak, not a bugfix. This will have negative impact on
users upgrading from 4.14.309 and 4.14.310, because you can be pretty
sure someone out there uses the "old" interface in their
application. I'm probably responsible for that sin in millipixels
fork.
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
(added patch authors to cc)
> > This is the start of the stable review cycle for the 4.14.310 release.
> > There are 20 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.
>
> > Dmitry Baryshkov <[email protected]>
> > clk: qcom: mmcc-apq8084: remove spdm clocks
>
> This looks like a cleanup, we should not need it in stable.
>
> > Paul Elder <[email protected]>
> > media: ov5640: Fix analogue gain control
>
> This is an API tweak, not a bugfix. This will have negative impact on
> users upgrading from 4.14.309 and 4.14.310, because you can be pretty
> sure someone out there uses the "old" interface in their
> application. I'm probably responsible for that sin in millipixels
> fork.
>
> Best regards,
> Pavel
>
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
On 16/03/2023 11:00, Pavel Machek wrote:
> (added patch authors to cc)
>
>>> This is the start of the stable review cycle for the 4.14.310 release.
>>> There are 20 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.
>>
>>> Dmitry Baryshkov <[email protected]>
>>> clk: qcom: mmcc-apq8084: remove spdm clocks
>>
>> This looks like a cleanup, we should not need it in stable.
Totally agree here.
>>
>>> Paul Elder <[email protected]>
>>> media: ov5640: Fix analogue gain control
>>
>> This is an API tweak, not a bugfix. This will have negative impact on
>> users upgrading from 4.14.309 and 4.14.310, because you can be pretty
>> sure someone out there uses the "old" interface in their
>> application. I'm probably responsible for that sin in millipixels
>> fork.
>>
>> Best regards,
>> Pavel
>>
>
>
>
--
With best wishes
Dmitry
On Thu, Mar 16, 2023 at 09:58:56AM +0100, Pavel Machek wrote:
> Hi!
>
> > This is the start of the stable review cycle for the 4.14.310 release.
> > There are 20 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.
>
> > Dmitry Baryshkov <[email protected]>
> > clk: qcom: mmcc-apq8084: remove spdm clocks
>
> This looks like a cleanup, we should not need it in stable.
Now removed.
> > Paul Elder <[email protected]>
> > media: ov5640: Fix analogue gain control
>
> This is an API tweak, not a bugfix. This will have negative impact on
> users upgrading from 4.14.309 and 4.14.310, because you can be pretty
> sure someone out there uses the "old" interface in their
> application. I'm probably responsible for that sin in millipixels
> fork.
They would have the same "impact" when moving to a newer kernel anyway,
so this seems like a valid bugfix to me.
thanks,
greg k-h
On Thu, Mar 16, 2023 at 11:01:01AM +0200, Dmitry Baryshkov wrote:
> On 16/03/2023 11:00, Pavel Machek wrote:
> > (added patch authors to cc)
> >
> > > > This is the start of the stable review cycle for the 4.14.310 release.
> > > > There are 20 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.
> > >
> > > > Dmitry Baryshkov <[email protected]>
> > > > clk: qcom: mmcc-apq8084: remove spdm clocks
> > >
> > > This looks like a cleanup, we should not need it in stable.
>
> Totally agree here.
Now dropped, thanks.
greg k-h
Hello Greg,
> From: Greg Kroah-Hartman <[email protected]>
> Sent: 16 March 2023 08:50
>
> This is the start of the stable review cycle for the 4.14.310 release.
> There are 20 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 Sat, 18 Mar 2023 08:33:04 +0000.
> Anything received after that time might be too late.
It sounds like there may be an -rc3 on the way, but for what it's worth...
CIP configurations built and booted with Linux 4.14.310-rc2 (12379b7d143a):
https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines/808352628
https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/commits/linux-4.14.y
Tested-by: Chris Paterson (CIP) <[email protected]>
Kind regards, Chris
On Thu, Mar 16, 2023 at 11:25:29AM +0000, Chris Paterson wrote:
> Hello Greg,
>
> > From: Greg Kroah-Hartman <[email protected]>
> > Sent: 16 March 2023 08:50
> >
> > This is the start of the stable review cycle for the 4.14.310 release.
> > There are 20 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 Sat, 18 Mar 2023 08:33:04 +0000.
> > Anything received after that time might be too late.
>
> It sounds like there may be an -rc3 on the way, but for what it's worth...
There is? Only for 4.19.y.
thanks,
greg k-h
Hello Greg,
> From: Greg Kroah-Hartman <[email protected]>
> Sent: 16 March 2023 11:34
>
> On Thu, Mar 16, 2023 at 11:25:29AM +0000, Chris Paterson wrote:
> > Hello Greg,
> >
> > > From: Greg Kroah-Hartman <[email protected]>
> > > Sent: 16 March 2023 08:50
> > >
> > > This is the start of the stable review cycle for the 4.14.310 release.
> > > There are 20 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 Sat, 18 Mar 2023 08:33:04 +0000.
> > > Anything received after that time might be too late.
> >
> > It sounds like there may be an -rc3 on the way, but for what it's worth...
>
> There is? Only for 4.19.y.
Ah, I was referring to you saying you'd drop "clk: qcom: mmcc-apq8084: remove spdm clocks".
I was assuming that meant another RC.
/me must stop assuming things...
Chris
On Thu, Mar 16, 2023 at 11:57:55AM +0000, Chris Paterson wrote:
> Hello Greg,
>
> > From: Greg Kroah-Hartman <[email protected]>
> > Sent: 16 March 2023 11:34
> >
> > On Thu, Mar 16, 2023 at 11:25:29AM +0000, Chris Paterson wrote:
> > > Hello Greg,
> > >
> > > > From: Greg Kroah-Hartman <[email protected]>
> > > > Sent: 16 March 2023 08:50
> > > >
> > > > This is the start of the stable review cycle for the 4.14.310 release.
> > > > There are 20 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 Sat, 18 Mar 2023 08:33:04 +0000.
> > > > Anything received after that time might be too late.
> > >
> > > It sounds like there may be an -rc3 on the way, but for what it's worth...
> >
> > There is? Only for 4.19.y.
>
> Ah, I was referring to you saying you'd drop "clk: qcom: mmcc-apq8084: remove spdm clocks".
> I was assuming that meant another RC.
> /me must stop assuming things...
Dropping a patch that is not causing build or test errors generally does
not mean a new -rc is to be released .
thanks,
greg k-h
On Thu, Mar 16, 2023 at 09:49:41AM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.310 release.
> There are 20 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 Sat, 18 Mar 2023 08:33:04 +0000.
> Anything received after that time might be too late.
>
Build results:
total: 168 pass: 168 fail: 0
Qemu test results:
total: 430 pass: 430 fail: 0
Tested-by: Guenter Roeck <[email protected]>
Guenter
On Thu, 16 Mar 2023 at 14:19, Greg Kroah-Hartman
<[email protected]> wrote:
>
> This is the start of the stable review cycle for the 4.14.310 release.
> There are 20 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 Sat, 18 Mar 2023 08:33:04 +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.14.310-rc2.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.14.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 <[email protected]>
## Build
* kernel: 4.14.310-rc2
* git: https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc
* git branch: linux-4.14.y
* git commit: 12379b7d143a8f0f07b4c069202ed684212ecacc
* git describe: v4.14.308-25-g12379b7d143a
* test details:
https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-4.14.y/build/v4.14.308-25-g12379b7d143a
## Test Regressions (compared to v4.14.308)
## Metric Regressions (compared to v4.14.308)
## Test Fixes (compared to v4.14.308)
## Metric Fixes (compared to v4.14.308)
## Test result summary
total: 72731, pass: 62239, fail: 2894, skip: 7289, xfail: 309
## Build Summary
* arc: 10 total, 10 passed, 0 failed
* arm: 199 total, 197 passed, 2 failed
* arm64: 37 total, 35 passed, 2 failed
* i386: 29 total, 28 passed, 1 failed
* mips: 41 total, 41 passed, 0 failed
* parisc: 12 total, 12 passed, 0 failed
* powerpc: 20 total, 19 passed, 1 failed
* s390: 15 total, 11 passed, 4 failed
* sh: 24 total, 24 passed, 0 failed
* sparc: 12 total, 12 passed, 0 failed
* x86_64: 34 total, 33 passed, 1 failed
## Test suites summary
* boot
* fwts
* kselftest-android
* kselftest-arm64
* kselftest-breakpoints
* kselftest-capabilities
* kselftest-cgroup
* kselftest-clone3
* kselftest-core
* kselftest-cpu-hotplug
* kselftest-cpufreq
* kselftest-drivers-dma-buf
* kselftest-efivarfs
* kselftest-filesystems
* kselftest-filesystems-binderfs
* kselftest-firmware
* kselftest-fpu
* kselftest-ftrace
* kselftest-futex
* kselftest-gpio
* kselftest-intel_pstate
* kselftest-ipc
* kselftest-ir
* kselftest-kcmp
* kselftest-kexec
* kselftest-kvm
* kselftest-lib
* kselftest-livepatch
* kselftest-membarrier
* kselftest-net
* kselftest-net-forwarding
* kselftest-net-mptcp
* kselftest-netfilter
* kselftest-nsfs
* kselftest-openat2
* kselftest-pid_namespace
* kselftest-pidfd
* kselftest-proc
* kselftest-pstore
* kselftest-ptrace
* kselftest-seccomp
* kselftest-sigaltstack
* kselftest-size
* kselftest-splice
* kselftest-static_keys
* kselftest-sync
* kselftest-sysctl
* kselftest-tc-testing
* kselftest-timens
* kselftest-timers
* kselftest-tmpfs
* kselftest-tpm2
* kselftest-user
* kselftest-vm
* kselftest-x86
* kselftest-zram
* kunit
* kvm-unit-tests
* libhugetlbfs
* log-parser-boot
* log-parser-test
* ltp-cap_bounds
* ltp-commands
* ltp-containers
* ltp-controllers
* ltp-cpuhotplug
* ltp-crypto
* ltp-cve
* ltp-dio
* ltp-fcntl-locktests
* ltp-filecaps
* ltp-fs
* ltp-fs_bind
* ltp-fs_perms_simple
* ltp-fsx
* ltp-hugetlb
* ltp-io
* ltp-ipc
* ltp-math
* ltp-mm
* ltp-nptl
* ltp-open-posix-tests
* ltp-pty
* ltp-sched
* ltp-securebits
* ltp-smoke
* ltp-syscalls
* ltp-tracing
* network-basic-tests
* packetdrill
* rcutorture
* v4l2-compliance
* vdso
--
Linaro LKFT
https://lkft.linaro.org