This is the start of the stable review cycle for the 5.10.3 release. There are 40 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, 25 Dec 2020 15:05:02 +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/v5.x/stable-review/patch-5.10.3-rc1.... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.10.y and the diffstat can be found below.
thanks,
greg k-h
------------- Pseudo-Shortlog of commits:
Greg Kroah-Hartman gregkh@linuxfoundation.org Linux 5.10.3-rc1
Dae R. Jeong dae.r.jeong@kaist.ac.kr md: fix a warning caused by a race between concurrent md_ioctl()s
Anant Thazhemadam anant.thazhemadam@gmail.com nl80211: validate key indexes for cfg80211_registered_device
Eric Biggers ebiggers@google.com crypto: af_alg - avoid undefined behavior accessing salg_name
Antti Palosaari crope@iki.fi media: msi2500: assign SPI bus number dynamically
Anant Thazhemadam anant.thazhemadam@gmail.com fs: quota: fix array-index-out-of-bounds bug by passing correct argument to vfs_cleanup_quota_inode()
Jan Kara jack@suse.cz quota: Sanity-check quota file headers on load
Peilin Ye yepeilin.cs@gmail.com Bluetooth: Fix slab-out-of-bounds read in hci_le_direct_adv_report_evt()
Eric Biggers ebiggers@google.com f2fs: prevent creating duplicate encrypted filenames
Eric Biggers ebiggers@google.com ext4: prevent creating duplicate encrypted filenames
Eric Biggers ebiggers@google.com ubifs: prevent creating duplicate encrypted filenames
Eric Biggers ebiggers@google.com fscrypt: add fscrypt_is_nokey_name()
Eric Biggers ebiggers@google.com fscrypt: remove kernel-internal constants from UAPI header
Alexey Kardashevskiy aik@ozlabs.ru serial_core: Check for port state when tty is in error state
Julian Sax jsbc@gmx.de HID: i2c-hid: add Vero K147 to descriptor override
Arnd Bergmann arnd@arndb.de scsi: megaraid_sas: Check user-provided offsets
Jack Qiu jack.qiu@huawei.com f2fs: init dirty_secmap incorrectly
Chao Yu chao@kernel.org f2fs: fix to seek incorrect data offset in inline data file
Suzuki K Poulose suzuki.poulose@arm.com coresight: etm4x: Handle TRCVIPCSSCTLR accesses
Suzuki K Poulose suzuki.poulose@arm.com coresight: etm4x: Fix accesses to TRCPROCSELR
Suzuki K Poulose suzuki.poulose@arm.com coresight: etm4x: Fix accesses to TRCCIDCTLR1
Suzuki K Poulose suzuki.poulose@arm.com coresight: etm4x: Fix accesses to TRCVMIDCTLR1
Sai Prakash Ranjan saiprakash.ranjan@codeaurora.org coresight: etm4x: Skip setting LPOVERRIDE bit for qcom, skip-power-up
Sai Prakash Ranjan saiprakash.ranjan@codeaurora.org coresight: etb10: Fix possible NULL ptr dereference in etb_enable_perf()
Suzuki K Poulose suzuki.poulose@arm.com coresight: tmc-etr: Fix barrier packet insertion for perf buffer
Mao Jinlong jinlmao@codeaurora.org coresight: tmc-etr: Check if page is valid before dma_map_page()
Sai Prakash Ranjan saiprakash.ranjan@codeaurora.org coresight: tmc-etf: Fix NULL ptr dereference in tmc_enable_etf_sink_perf()
Krzysztof Kozlowski krzk@kernel.org ARM: dts: exynos: fix USB 3.0 pins supply being turned off on Odroid XU
Krzysztof Kozlowski krzk@kernel.org ARM: dts: exynos: fix USB 3.0 VBUS control and over-current pins on Exynos5410
Krzysztof Kozlowski krzk@kernel.org ARM: dts: exynos: fix roles of USB 3.0 ports on Odroid XU
Fabio Estevam festevam@gmail.com usb: chipidea: ci_hdrc_imx: Pass DISABLE_DEVICE_STREAMING flag to imx6ul
Will McVicker willmcvicker@google.com USB: gadget: f_rndis: fix bitrate for SuperSpeed and above
Jack Pham jackp@codeaurora.org usb: gadget: f_fs: Re-use SS descriptors for SuperSpeedPlus
Will McVicker willmcvicker@google.com USB: gadget: f_midi: setup SuperSpeed Plus descriptors
taehyun.cho taehyun.cho@samsung.com USB: gadget: f_acm: add support for SuperSpeed Plus
Johan Hovold johan@kernel.org USB: serial: option: add interface-number sanity check to flag handling
Dan Carpenter dan.carpenter@oracle.com usb: mtu3: fix memory corruption in mtu3_debugfs_regset()
Nicolin Chen nicoleotsuka@gmail.com soc/tegra: fuse: Fix index bug in get_process_id
Artem Labazov 123321artyom@gmail.com exfat: Avoid allocating upcase table using kcalloc()
Andi Kleen ak@linux.intel.com x86/split-lock: Avoid returning with interrupts enabled
Thierry Reding treding@nvidia.com net: ipconfig: Avoid spurious blank lines in boot log
-------------
Diffstat:
Makefile | 4 +- arch/arm/boot/dts/exynos5410-odroidxu.dts | 6 ++- arch/arm/boot/dts/exynos5410-pinctrl.dtsi | 28 ++++++++++++ arch/arm/boot/dts/exynos5410.dtsi | 4 ++ arch/x86/kernel/traps.c | 3 +- crypto/af_alg.c | 10 +++-- drivers/hid/i2c-hid/i2c-hid-dmi-quirks.c | 8 ++++ drivers/hwtracing/coresight/coresight-etb10.c | 4 +- drivers/hwtracing/coresight/coresight-etm4x-core.c | 41 ++++++++++------- drivers/hwtracing/coresight/coresight-priv.h | 2 + drivers/hwtracing/coresight/coresight-tmc-etf.c | 4 +- drivers/hwtracing/coresight/coresight-tmc-etr.c | 4 +- drivers/md/md.c | 7 ++- drivers/media/usb/msi2500/msi2500.c | 2 +- drivers/scsi/megaraid/megaraid_sas_base.c | 16 ++++--- drivers/soc/tegra/fuse/speedo-tegra210.c | 2 +- drivers/tty/serial/serial_core.c | 4 ++ drivers/usb/chipidea/ci_hdrc_imx.c | 3 +- drivers/usb/gadget/function/f_acm.c | 2 +- drivers/usb/gadget/function/f_fs.c | 5 ++- drivers/usb/gadget/function/f_midi.c | 6 +++ drivers/usb/gadget/function/f_rndis.c | 4 +- drivers/usb/mtu3/mtu3_debugfs.c | 2 +- drivers/usb/serial/option.c | 23 +++++++++- fs/crypto/fscrypt_private.h | 9 ++-- fs/crypto/hooks.c | 5 ++- fs/crypto/keyring.c | 2 +- fs/crypto/keysetup.c | 4 +- fs/crypto/policy.c | 5 ++- fs/exfat/nls.c | 6 +-- fs/ext4/namei.c | 3 ++ fs/f2fs/f2fs.h | 2 + fs/f2fs/file.c | 11 +++-- fs/f2fs/segment.c | 2 +- fs/quota/dquot.c | 2 +- fs/quota/quota_v2.c | 19 ++++++++ fs/ubifs/dir.c | 17 ++++++-- include/linux/fscrypt.h | 34 +++++++++++++++ include/uapi/linux/fscrypt.h | 5 +-- include/uapi/linux/if_alg.h | 16 +++++++ net/bluetooth/hci_event.c | 12 +++-- net/ipv4/ipconfig.c | 14 +++--- net/wireless/core.h | 2 + net/wireless/nl80211.c | 7 +-- net/wireless/util.c | 51 ++++++++++++++++++---- 45 files changed, 334 insertions(+), 88 deletions(-)
On Wed, 23 Dec 2020 16:33:01 +0100, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.10.3 release. There are 40 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, 25 Dec 2020 15:05:02 +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/v5.x/stable-review/patch-5.10.3-rc1.... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.10.y and the diffstat can be found below.
thanks,
greg k-h
All tests passing for Tegra ...
Test results for stable-v5.10: 12 builds: 12 pass, 0 fail 26 boots: 26 pass, 0 fail 64 tests: 64 pass, 0 fail
Linux version: 5.10.3-rc1-ga5ba578b5228 Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000, tegra194-p2972-0000, tegra20-ventana, tegra210-p2371-2180, tegra210-p3450-0000, tegra30-cardhu-a04
Tested-by: Jon Hunter jonathanh@nvidia.com
Jon
On Wed, Dec 23, 2020 at 07:26:38PM +0000, Jon Hunter wrote:
On Wed, 23 Dec 2020 16:33:01 +0100, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.10.3 release. There are 40 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, 25 Dec 2020 15:05:02 +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/v5.x/stable-review/patch-5.10.3-rc1.... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.10.y and the diffstat can be found below.
thanks,
greg k-h
All tests passing for Tegra ...
Test results for stable-v5.10: 12 builds: 12 pass, 0 fail 26 boots: 26 pass, 0 fail 64 tests: 64 pass, 0 fail
Linux version: 5.10.3-rc1-ga5ba578b5228 Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000, tegra194-p2972-0000, tegra20-ventana, tegra210-p2371-2180, tegra210-p3450-0000, tegra30-cardhu-a04
Tested-by: Jon Hunter jonathanh@nvidia.com
Thanks for testing and letting me know.
greg k-h
Hello!
On 12/23/20 9:33 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.10.3 release. There are 40 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, 25 Dec 2020 15:05:02 +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/v5.x/stable-review/patch-5.10.3-rc1.... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.10.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
Summary ------------------------------------------------------------------------
kernel: 5.10.3-rc1 git repo: ['https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git', 'https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc'] git branch: linux-5.10.y git commit: a5ba578b52286e2a855f6b172c851d7afbf68e60 git describe: v5.10.2-41-ga5ba578b5228 Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-5.10.y/build/v5.10....
No regressions (compared to build v5.10.2)
No fixes (compared to build v5.10.2)
Ran 50032 total tests in the following environments and test suites.
Environments -------------- - arc - arm - arm64 - dragonboard-410c - hi6220-hikey - i386 - juno-r2 - juno-r2-compat - juno-r2-kasan - mips - parisc - powerpc - qemu-arm-clang - qemu-arm64-clang - qemu-arm64-kasan - qemu-i386-clang - qemu-x86_64-clang - qemu-x86_64-kasan - qemu-x86_64-kcsan - qemu_arm - qemu_arm64 - qemu_arm64-compat - qemu_i386 - qemu_x86_64 - qemu_x86_64-compat - riscv - s390 - sh - sparc - x15 - x86 - x86-kasan
Test Suites ----------- * build * fwts * install-android-platform-tools-r2600 * kselftest * kselftest-vsyscall-mode-native * kselftest-vsyscall-mode-none * kunit * 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_bind-tests * ltp-fs_perms_simple-tests * ltp-fs-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 * perf * rcutorture * v4l2-compliance
Happy holidays, greetings!
Daniel Díaz daniel.diaz@linaro.org
On Wed, Dec 23, 2020 at 06:56:56PM -0600, Daniel Díaz wrote:
Hello!
On 12/23/20 9:33 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.10.3 release. There are 40 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, 25 Dec 2020 15:05:02 +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/v5.x/stable-review/patch-5.10.3-rc1.... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.10.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
Thanks for testing!
greg k-h
On Wed, 2020-12-23 at 16:33 +0100, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.10.3 release. There are 40 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, 25 Dec 2020 15:05:02 +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/v5.x/stable-review/patch-5.10.3-rc1.... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux- stable-rc.git linux-5.10.y and the diffstat can be found below.
thanks,
greg k-h
hello , Compiled and booted 5.10.3-rc1+.
dmesg -l err gives... --------------x-------------x-------------------> 43.190922] Bluetooth: hci0: don't support firmware rome 0x31010100 --------------x---------------x----------------->
My Bluetooth is Off.
Tested-by: Jeffrin Jose T jeffrin@rajagiritech.edu.in
On Thu, Dec 24, 2020 at 03:13:38PM +0530, Jeffrin Jose T wrote:
On Wed, 2020-12-23 at 16:33 +0100, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.10.3 release. There are 40 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, 25 Dec 2020 15:05:02 +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/v5.x/stable-review/patch-5.10.3-rc1.... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux- stable-rc.git linux-5.10.y and the diffstat can be found below.
thanks,
greg k-h
hello , Compiled and booted 5.10.3-rc1+.
dmesg -l err gives... --------------x-------------x-------------------> 43.190922] Bluetooth: hci0: don't support firmware rome 0x31010100 --------------x---------------x----------------->
My Bluetooth is Off.
Is this a new warning? Does it show up on 5.10.2?
Tested-by: Jeffrin Jose T jeffrin@rajagiritech.edu.in
thanks for testing?
greg k-h
On Sat, 2020-12-26 at 16:06 +0100, Greg Kroah-Hartman wrote:
On Thu, Dec 24, 2020 at 03:13:38PM +0530, Jeffrin Jose T wrote:
On Wed, 2020-12-23 at 16:33 +0100, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.10.3 release. There are 40 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, 25 Dec 2020 15:05:02 +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/v5.x/stable-review/patch-5.10.3-rc1.... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linu x- stable-rc.git linux-5.10.y and the diffstat can be found below.
thanks,
greg k-h
hello , Compiled and booted 5.10.3-rc1+.
dmesg -l err gives... --------------x-------------x-------------------> 43.190922] Bluetooth: hci0: don't support firmware rome 0x31010100 --------------x---------------x----------------->
My Bluetooth is Off.
Is this a new warning? Does it show up on 5.10.2?
Tested-by: Jeffrin Jose T jeffrin@rajagiritech.edu.in
thanks for testing?
greg k-h
this does not show up in 5.10.2-rc1+
On Sun, Dec 27, 2020 at 09:20:07PM +0530, Jeffrin Jose T wrote:
On Sat, 2020-12-26 at 16:06 +0100, Greg Kroah-Hartman wrote:
On Thu, Dec 24, 2020 at 03:13:38PM +0530, Jeffrin Jose T wrote:
On Wed, 2020-12-23 at 16:33 +0100, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.10.3 release. There are 40 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, 25 Dec 2020 15:05:02 +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/v5.x/stable-review/patch-5.10.3-rc1.... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linu x- stable-rc.git linux-5.10.y and the diffstat can be found below.
thanks,
greg k-h
hello , Compiled and booted 5.10.3-rc1+.
dmesg -l err gives... --------------x-------------x-------------------> 43.190922] Bluetooth: hci0: don't support firmware rome 0x31010100 --------------x---------------x----------------->
My Bluetooth is Off.
Is this a new warning? Does it show up on 5.10.2?
Tested-by: Jeffrin Jose T jeffrin@rajagiritech.edu.in
thanks for testing?
greg k-h
this does not show up in 5.10.2-rc1+
Odd. Can you run 'git bisect' to find the offending commit?
Does this same error message show up in Linus's git tree?
thanks,
greg k-h
On Sun, 2020-12-27 at 17:05 +0100, Greg Kroah-Hartman wrote:
On Sun, Dec 27, 2020 at 09:20:07PM +0530, Jeffrin Jose T wrote:
On Sat, 2020-12-26 at 16:06 +0100, Greg Kroah-Hartman wrote:
On Thu, Dec 24, 2020 at 03:13:38PM +0530, Jeffrin Jose T wrote:
On Wed, 2020-12-23 at 16:33 +0100, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.10.3 release. There are 40 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, 25 Dec 2020 15:05:02 +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/v5.x/stable-review/patch-5.10.3-rc1.... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/ linu x- stable-rc.git linux-5.10.y and the diffstat can be found below.
thanks,
greg k-h
hello , Compiled and booted 5.10.3-rc1+.
dmesg -l err gives... --------------x-------------x-------------------> 43.190922] Bluetooth: hci0: don't support firmware rome 0x31010100 --------------x---------------x----------------->
My Bluetooth is Off.
Is this a new warning? Does it show up on 5.10.2?
Tested-by: Jeffrin Jose T jeffrin@rajagiritech.edu.in
thanks for testing?
greg k-h
this does not show up in 5.10.2-rc1+
Odd. Can you run 'git bisect' to find the offending commit?
Does this same error message show up in Linus's git tree?
thanks,
greg k-h
i will try to do "git bisect" . i saw this error in linus's tree.
Hi!
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.3-rc1.... or in the git tree and branch at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/ linu x- stable-rc.git linux-5.10.y and the diffstat can be found below.
thanks,
greg k-h
hello , Compiled and booted 5.10.3-rc1+.
dmesg -l err gives... --------------x-------------x-------------------> 43.190922] Bluetooth: hci0: don't support firmware rome 0x31010100 --------------x---------------x----------------->
My Bluetooth is Off.
Is this a new warning? Does it show up on 5.10.2?
Tested-by: Jeffrin Jose T jeffrin@rajagiritech.edu.in
thanks for testing?
greg k-h
this does not show up in 5.10.2-rc1+
Odd. Can you run 'git bisect' to find the offending commit?
Does this same error message show up in Linus's git tree?
i will try to do "git bisect" . i saw this error in linus's tree.
The bug is in -stable, too, so it is probably easiest to do bisect on -stable tree. IIRC there's less then few hundred commits, so it should be feasible to do bisection by hand if you are not familiar with git bisect.
Best regards, Pavel
On 12/28/20 1:50 AM, Pavel Machek wrote:
Hi!
> https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.3-rc1.... > or in the git tree and branch at: > git://git.kernel.org/pub/scm/linux/kernel/git/stable/ > linu > x- > stable-rc.git linux-5.10.y > and the diffstat can be found below. > > thanks, > > greg k-h
hello , Compiled and booted 5.10.3-rc1+.
dmesg -l err gives... --------------x-------------x-------------------> 43.190922] Bluetooth: hci0: don't support firmware rome 0x31010100 --------------x---------------x----------------->
My Bluetooth is Off.
Is this a new warning? Does it show up on 5.10.2?
Tested-by: Jeffrin Jose T jeffrin@rajagiritech.edu.in
thanks for testing?
greg k-h
this does not show up in 5.10.2-rc1+
Odd. Can you run 'git bisect' to find the offending commit?
Does this same error message show up in Linus's git tree?
i will try to do "git bisect" . i saw this error in linus's tree.
The bug is in -stable, too, so it is probably easiest to do bisect on -stable tree. IIRC there's less then few hundred commits, so it should be feasible to do bisection by hand if you are not familiar with git bisect.
My wild guess would be commit b260e4a68853 ("Bluetooth: Fix slab-out-of-bounds read in hci_le_direct_adv_report_evt()"), but I don't see what might be wrong with it unless some BT device sends a bad report which used to be accepted but is now silently ignored.
Guenter
On Mon, 2020-12-28 at 12:41 -0800, Guenter Roeck wrote:
On 12/28/20 1:50 AM, Pavel Machek wrote:
Hi!
> > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.3-rc1.... > > or in the git tree and branch at: > > git://git.kernel.org/pub/scm/linux/kernel/git/s > > table/ > > linu > > x- > > stable-rc.git linux-5.10.y > > and the diffstat can be found below. > > > > thanks, > > > > greg k-h > > hello , > Compiled and booted 5.10.3-rc1+. > > dmesg -l err gives... > --------------x-------------x-------------------> > 43.190922] Bluetooth: hci0: don't support firmware > rome > 0x31010100 > --------------x---------------x-----------------> > > My Bluetooth is Off.
Is this a new warning? Does it show up on 5.10.2?
> Tested-by: Jeffrin Jose T jeffrin@rajagiritech.edu.in
thanks for testing?
greg k-h
this does not show up in 5.10.2-rc1+
Odd. Can you run 'git bisect' to find the offending commit?
Does this same error message show up in Linus's git tree?
i will try to do "git bisect" . i saw this error in linus's tree.
The bug is in -stable, too, so it is probably easiest to do bisect on -stable tree. IIRC there's less then few hundred commits, so it should be feasible to do bisection by hand if you are not familiar with git bisect.
My wild guess would be commit b260e4a68853 ("Bluetooth: Fix slab-out- of-bounds read in hci_le_direct_adv_report_evt()"), but I don't see what might be wrong with it unless some BT device sends a bad report which used to be accepted but is now silently ignored.
Guenter
hello,
Did "git bisect" in a typically ok fashion and found that 5.9.0 is working for bluetooth related. But 5.10.0-rc1 related is not working.
some related information in bisect.txt attached.
On Sun, Jan 03, 2021 at 06:37:51PM +0530, Jeffrin Jose T wrote:
On Mon, 2020-12-28 at 12:41 -0800, Guenter Roeck wrote:
On 12/28/20 1:50 AM, Pavel Machek wrote:
Hi!
> > > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.3-rc1.... > > > or in the git tree and branch at: > > > git://git.kernel.org/pub/scm/linux/kernel/git/s > > > table/ > > > linu > > > x- > > > stable-rc.git linux-5.10.y > > > and the diffstat can be found below. > > > > > > thanks, > > > > > > greg k-h > > > > hello , > > Compiled and booted 5.10.3-rc1+. > > > > dmesg -l err gives... > > --------------x-------------x-------------------> > > 43.190922] Bluetooth: hci0: don't support firmware > > rome > > 0x31010100 > > --------------x---------------x-----------------> > > > > My Bluetooth is Off. > > Is this a new warning? Does it show up on 5.10.2? > > > Tested-by: Jeffrin Jose T jeffrin@rajagiritech.edu.in > > thanks for testing? > > greg k-h
this does not show up in 5.10.2-rc1+
Odd. Can you run 'git bisect' to find the offending commit?
Does this same error message show up in Linus's git tree?
i will try to do "git bisect" . i saw this error in linus's tree.
The bug is in -stable, too, so it is probably easiest to do bisect on -stable tree. IIRC there's less then few hundred commits, so it should be feasible to do bisection by hand if you are not familiar with git bisect.
My wild guess would be commit b260e4a68853 ("Bluetooth: Fix slab-out- of-bounds read in hci_le_direct_adv_report_evt()"), but I don't see what might be wrong with it unless some BT device sends a bad report which used to be accepted but is now silently ignored.
Guenter
hello,
Did "git bisect" in a typically ok fashion and found that 5.9.0 is working for bluetooth related. But 5.10.0-rc1 related is not working.
some related information in bisect.txt attached.
-- software engineer rajagiri school of engineering and technology - autonomous
$sudo git bisect bad Bisecting: 0 revisions left to test after this (roughly 1 step) [194810f78402128fe07676646cf9027fd3ed431c] dt-bindings: leds: Update devicetree documents for ID_RGB
$sudo git bisect bad Bisecting: 0 revisions left to test after this (roughly 0 steps) [3650b228f83adda7e5ee532e2b90429c03f7b9ec] Linux 5.10-rc1
That's really odd, as that commit only has a Makefile change.
Also, why run this as root?
greg k-h
On Mon, 2021-01-04 at 07:21 +0100, Greg Kroah-Hartman wrote:
On Sun, Jan 03, 2021 at 06:37:51PM +0530, Jeffrin Jose T wrote:
On Mon, 2020-12-28 at 12:41 -0800, Guenter Roeck wrote:
On 12/28/20 1:50 AM, Pavel Machek wrote:
Hi!
> > > > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.3-rc1.... > > > > or in the git tree and branch at: > > > > git://git.kernel.org/pub/scm/linux/kernel/g > > > > it/s > > > > table/ > > > > linu > > > > x- > > > > stable-rc.git linux-5.10.y > > > > and the diffstat can be found below. > > > > > > > > thanks, > > > > > > > > greg k-h > > > > > > hello , > > > Compiled and booted 5.10.3-rc1+. > > > > > > dmesg -l err gives... > > > --------------x-------------x-------------------> > > > 43.190922] Bluetooth: hci0: don't support firmware > > > rome > > > 0x31010100 > > > --------------x---------------x-----------------> > > > > > > My Bluetooth is Off. > > > > Is this a new warning? Does it show up on 5.10.2? > > > > > Tested-by: Jeffrin Jose T < > > > jeffrin@rajagiritech.edu.in> > > > > thanks for testing? > > > > greg k-h > > this does not show up in 5.10.2-rc1+
Odd. Can you run 'git bisect' to find the offending commit?
Does this same error message show up in Linus's git tree?
i will try to do "git bisect" . i saw this error in linus's tree.
The bug is in -stable, too, so it is probably easiest to do bisect on -stable tree. IIRC there's less then few hundred commits, so it should be feasible to do bisection by hand if you are not familiar with git bisect.
My wild guess would be commit b260e4a68853 ("Bluetooth: Fix slab- out- of-bounds read in hci_le_direct_adv_report_evt()"), but I don't see what might be wrong with it unless some BT device sends a bad report which used to be accepted but is now silently ignored.
Guenter
hello,
Did "git bisect" in a typically ok fashion and found that 5.9.0 is working for bluetooth related. But 5.10.0-rc1 related is not working.
some related information in bisect.txt attached.
-- software engineer rajagiri school of engineering and technology - autonomous
$sudo git bisect bad Bisecting: 0 revisions left to test after this (roughly 1 step) [194810f78402128fe07676646cf9027fd3ed431c] dt-bindings: leds: Update devicetree documents for ID_RGB
$sudo git bisect bad Bisecting: 0 revisions left to test after this (roughly 0 steps) [3650b228f83adda7e5ee532e2b90429c03f7b9ec] Linux 5.10-rc1
That's really odd, as that commit only has a Makefile change.
i will try to work on it again
Also, why run this as root?
there may be some problem in my sudo configurtion or the way in run sudo.\ when i run "make modules_install" and "make install" using sudo typical files ownership changes to root.
On Thu, Jan 07, 2021 at 01:08:01AM +0530, Jeffrin Jose T wrote:
On Mon, 2021-01-04 at 07:21 +0100, Greg Kroah-Hartman wrote:
On Sun, Jan 03, 2021 at 06:37:51PM +0530, Jeffrin Jose T wrote:
On Mon, 2020-12-28 at 12:41 -0800, Guenter Roeck wrote:
On 12/28/20 1:50 AM, Pavel Machek wrote:
Hi!
> > > > > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.3-rc1.... > > > > > or in the git tree and branch at: > > > > > git://git.kernel.org/pub/scm/linux/kernel/g > > > > > it/s > > > > > table/ > > > > > linu > > > > > x- > > > > > stable-rc.git linux-5.10.y > > > > > and the diffstat can be found below. > > > > > > > > > > thanks, > > > > > > > > > > greg k-h > > > > > > > > hello , > > > > Compiled and booted 5.10.3-rc1+. > > > > > > > > dmesg -l err gives... > > > > --------------x-------------x-------------------> > > > > 43.190922] Bluetooth: hci0: don't support firmware > > > > rome > > > > 0x31010100 > > > > --------------x---------------x-----------------> > > > > > > > > My Bluetooth is Off. > > > > > > Is this a new warning? Does it show up on 5.10.2? > > > > > > > Tested-by: Jeffrin Jose T < > > > > jeffrin@rajagiritech.edu.in> > > > > > > thanks for testing? > > > > > > greg k-h > > > > this does not show up in 5.10.2-rc1+ > > Odd. Can you run 'git bisect' to find the offending > commit? > > Does this same error message show up in Linus's git tree?
i will try to do "git bisect" . i saw this error in linus's tree.
The bug is in -stable, too, so it is probably easiest to do bisect on -stable tree. IIRC there's less then few hundred commits, so it should be feasible to do bisection by hand if you are not familiar with git bisect.
My wild guess would be commit b260e4a68853 ("Bluetooth: Fix slab- out- of-bounds read in hci_le_direct_adv_report_evt()"), but I don't see what might be wrong with it unless some BT device sends a bad report which used to be accepted but is now silently ignored.
Guenter
hello,
Did "git bisect" in a typically ok fashion and found that 5.9.0 is working for bluetooth related. But 5.10.0-rc1 related is not working.
some related information in bisect.txt attached.
-- software engineer rajagiri school of engineering and technology - autonomous
$sudo git bisect bad Bisecting: 0 revisions left to test after this (roughly 1 step) [194810f78402128fe07676646cf9027fd3ed431c] dt-bindings: leds: Update devicetree documents for ID_RGB
$sudo git bisect bad Bisecting: 0 revisions left to test after this (roughly 0 steps) [3650b228f83adda7e5ee532e2b90429c03f7b9ec] Linux 5.10-rc1
That's really odd, as that commit only has a Makefile change.
i will try to work on it again
Also, why run this as root?
there may be some problem in my sudo configurtion or the way in run sudo.\ when i run "make modules_install" and "make install" using sudo typical files ownership changes to root.
That's fine when installing the kernel, but not when building or running git, please don't do that.
On Wed, 2021-01-06 at 20:49 +0100, Greg Kroah-Hartman wrote:
On Thu, Jan 07, 2021 at 01:08:01AM +0530, Jeffrin Jose T wrote:
On Mon, 2021-01-04 at 07:21 +0100, Greg Kroah-Hartman wrote:
On Sun, Jan 03, 2021 at 06:37:51PM +0530, Jeffrin Jose T wrote:
On Mon, 2020-12-28 at 12:41 -0800, Guenter Roeck wrote:
On 12/28/20 1:50 AM, Pavel Machek wrote:
Hi!
> > > > > > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.3-rc1.... > > > > > > or in the git tree and branch at: > > > > > > git://git.kernel.org/pub/scm/linux/kern > > > > > > el/g > > > > > > it/s > > > > > > table/ > > > > > > linu > > > > > > x- > > > > > > stable-rc.git linux-5.10.y > > > > > > and the diffstat can be found below. > > > > > > > > > > > > thanks, > > > > > > > > > > > > greg k-h > > > > > > > > > > hello , > > > > > Compiled and booted 5.10.3-rc1+. > > > > > > > > > > dmesg -l err gives... > > > > > --------------x-------------x-------------------> > > > > > 43.190922] Bluetooth: hci0: don't support > > > > > firmware > > > > > rome > > > > > 0x31010100 > > > > > --------------x---------------x-----------------> > > > > > > > > > > My Bluetooth is Off. > > > > > > > > Is this a new warning? Does it show up on 5.10.2? > > > > > > > > > Tested-by: Jeffrin Jose T < > > > > > jeffrin@rajagiritech.edu.in> > > > > > > > > thanks for testing? > > > > > > > > greg k-h > > > > > > this does not show up in 5.10.2-rc1+ > > > > Odd. Can you run 'git bisect' to find the offending > > commit? > > > > Does this same error message show up in Linus's git > > tree?
> i will try to do "git bisect" . i saw this error in > linus's > tree.
The bug is in -stable, too, so it is probably easiest to do bisect on -stable tree. IIRC there's less then few hundred commits, so it should be feasible to do bisection by hand if you are not familiar with git bisect.
My wild guess would be commit b260e4a68853 ("Bluetooth: Fix slab- out- of-bounds read in hci_le_direct_adv_report_evt()"), but I don't see what might be wrong with it unless some BT device sends a bad report which used to be accepted but is now silently ignored.
Guenter
hello,
Did "git bisect" in a typically ok fashion and found that 5.9.0 is working for bluetooth related. But 5.10.0-rc1 related is not working.
some related information in bisect.txt attached.
-- software engineer rajagiri school of engineering and technology - autonomous
$sudo git bisect bad Bisecting: 0 revisions left to test after this (roughly 1 step) [194810f78402128fe07676646cf9027fd3ed431c] dt-bindings: leds: Update devicetree documents for ID_RGB
$sudo git bisect bad Bisecting: 0 revisions left to test after this (roughly 0 steps) [3650b228f83adda7e5ee532e2b90429c03f7b9ec] Linux 5.10-rc1
That's really odd, as that commit only has a Makefile change.
i will try to work on it again
Also, why run this as root?
there may be some problem in my sudo configurtion or the way in run sudo.\ when i run "make modules_install" and "make install" using sudo typical files ownership changes to root.
That's fine when installing the kernel, but not when building or running git, please don't do that.
ok related .
On 12/23/20 7:33 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.10.3 release. There are 40 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, 25 Dec 2020 15:05:02 +0000. Anything received after that time might be too late.
Build results: total: 154 pass: 154 fail: 0 Qemu test results: total: 427 pass: 427 fail: 0
Tested-by: Guenter Roeck linux@roeck-us.net
Guenter
On Thu, Dec 24, 2020 at 07:26:45AM -0800, Guenter Roeck wrote:
On 12/23/20 7:33 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.10.3 release. There are 40 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, 25 Dec 2020 15:05:02 +0000. Anything received after that time might be too late.
Build results: total: 154 pass: 154 fail: 0 Qemu test results: total: 427 pass: 427 fail: 0
Tested-by: Guenter Roeck linux@roeck-us.net
Thanks for testing!
greg k-h
-
Daniel Díaz -
Greg Kroah-Hartman -
Guenter Roeck -
Jeffrin Jose T -
Jon Hunter -
Pavel Machek