From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-kernel@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
linux@roeck-us.net, shuah@kernel.org, patches@kernelci.org,
lkft-triage@lists.linaro.org, pavel@denx.de,
jonathanh@nvidia.com, f.fainelli@gmail.com,
stable@vger.kernel.org
Subject: [PATCH 4.4 00/14] 4.4.263-rc1 review
Date: Mon, 22 Mar 2021 13:28:54 +0100 [thread overview]
Message-ID: <20210322121919.202392464@linuxfoundation.org> (raw)
This is the start of the stable review cycle for the 4.4.263 release.
There are 14 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 Wed, 24 Mar 2021 12:19:09 +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.4.263-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.4.y
and the diffstat can be found below.
thanks,
greg k-h
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Linux 4.4.263-rc1
Thomas Gleixner <tglx@linutronix.de>
genirq: Disable interrupts for force threaded handlers
Shijie Luo <luoshijie1@huawei.com>
ext4: fix potential error in ext4_do_update_inode
zhangyi (F) <yi.zhang@huawei.com>
ext4: find old entry again if failed to rename whiteout
Thomas Gleixner <tglx@linutronix.de>
x86/ioapic: Ignore IRQ2 again
Tyrel Datwyler <tyreld@linux.ibm.com>
PCI: rpadlpar: Fix potential drc_name corruption in store functions
Jim Lin <jilin@nvidia.com>
usb: gadget: configfs: Fix KASAN use-after-free
Macpaul Lin <macpaul.lin@mediatek.com>
USB: replace hardcode maximum usb string length by definition
Dan Carpenter <dan.carpenter@oracle.com>
scsi: lpfc: Fix some error codes in debugfs
Joe Korty <joe.korty@concurrent-rt.com>
NFSD: Repair misuse of sv_lock in 5.10.16-rt30.
Filipe Manana <fdmanana@suse.com>
btrfs: fix race when cloning extent buffer during rewind of an old root
Gwendal Grignou <gwendal@chromium.org>
platform/chrome: cros_ec_dev - Fix security issue
Jan Kara <jack@suse.cz>
ext4: check journal inode extents more carefully
Jan Kara <jack@suse.cz>
ext4: don't allow overlapping system zones
Jan Kara <jack@suse.cz>
ext4: handle error of ext4_setup_system_zone() on remount
-------------
Diffstat:
Makefile | 4 +-
arch/x86/kernel/apic/io_apic.c | 10 +++++
drivers/pci/hotplug/rpadlpar_sysfs.c | 14 +++----
drivers/platform/chrome/cros_ec_dev.c | 4 ++
drivers/platform/chrome/cros_ec_proto.c | 4 +-
drivers/scsi/lpfc/lpfc_debugfs.c | 4 +-
drivers/usb/gadget/composite.c | 4 +-
drivers/usb/gadget/configfs.c | 16 +++++---
drivers/usb/gadget/usbstring.c | 4 +-
fs/btrfs/ctree.c | 2 +
fs/ext4/block_validity.c | 71 +++++++++++++++------------------
fs/ext4/ext4.h | 6 +--
fs/ext4/extents.c | 16 +++-----
fs/ext4/indirect.c | 6 +--
fs/ext4/inode.c | 13 +++---
fs/ext4/mballoc.c | 4 +-
fs/ext4/namei.c | 29 +++++++++++++-
fs/ext4/super.c | 5 ++-
include/linux/mfd/cros_ec.h | 6 ++-
include/uapi/linux/usb/ch9.h | 3 ++
kernel/irq/manage.c | 4 ++
net/sunrpc/svc_xprt.c | 4 +-
22 files changed, 139 insertions(+), 94 deletions(-)
next reply other threads:[~2021-03-22 12:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 12:28 Greg Kroah-Hartman [this message]
2021-03-22 12:28 ` [PATCH 4.4 01/14] ext4: handle error of ext4_setup_system_zone() on remount Greg Kroah-Hartman
2021-03-22 12:28 ` [PATCH 4.4 02/14] ext4: dont allow overlapping system zones Greg Kroah-Hartman
2021-03-22 12:28 ` [PATCH 4.4 03/14] ext4: check journal inode extents more carefully Greg Kroah-Hartman
2021-03-22 12:28 ` [PATCH 4.4 04/14] platform/chrome: cros_ec_dev - Fix security issue Greg Kroah-Hartman
2021-03-22 12:28 ` [PATCH 4.4 05/14] btrfs: fix race when cloning extent buffer during rewind of an old root Greg Kroah-Hartman
2021-03-22 12:29 ` [PATCH 4.4 06/14] NFSD: Repair misuse of sv_lock in 5.10.16-rt30 Greg Kroah-Hartman
2021-03-22 12:29 ` [PATCH 4.4 07/14] scsi: lpfc: Fix some error codes in debugfs Greg Kroah-Hartman
2021-03-22 12:29 ` [PATCH 4.4 08/14] USB: replace hardcode maximum usb string length by definition Greg Kroah-Hartman
2021-03-22 12:29 ` [PATCH 4.4 09/14] usb: gadget: configfs: Fix KASAN use-after-free Greg Kroah-Hartman
2021-03-22 12:29 ` [PATCH 4.4 10/14] PCI: rpadlpar: Fix potential drc_name corruption in store functions Greg Kroah-Hartman
2021-03-22 12:29 ` [PATCH 4.4 11/14] x86/ioapic: Ignore IRQ2 again Greg Kroah-Hartman
2021-03-22 12:29 ` [PATCH 4.4 12/14] ext4: find old entry again if failed to rename whiteout Greg Kroah-Hartman
2021-03-22 12:29 ` [PATCH 4.4 13/14] ext4: fix potential error in ext4_do_update_inode Greg Kroah-Hartman
2021-03-22 12:29 ` [PATCH 4.4 14/14] genirq: Disable interrupts for force threaded handlers Greg Kroah-Hartman
2021-03-22 14:35 ` [PATCH 4.4 00/14] 4.4.263-rc1 review Jon Hunter
2021-03-22 20:14 ` Pavel Machek
2021-03-22 21:55 ` Guenter Roeck
2021-03-23 13:30 ` Naresh Kamboju
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210322121919.202392464@linuxfoundation.org \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=f.fainelli@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=pavel@denx.de \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).