From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
torvalds@linux-foundation.org, stable@vger.kernel.org
Cc: lwn@lwn.net, jslaby@suse.cz,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Linux 4.4.263
Date: Wed, 24 Mar 2021 11:19:13 +0100 [thread overview]
Message-ID: <161658115316149@kroah.com> (raw)
I'm announcing the release of the 4.4.263 kernel.
All users of the 4.4 kernel series must upgrade.
The updated 4.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.4.y
and can be browsed at the normal kernel.org git web browser:
https://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary
thanks,
greg k-h
------------
Makefile | 2
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, 138 insertions(+), 93 deletions(-)
Dan Carpenter (1):
scsi: lpfc: Fix some error codes in debugfs
Filipe Manana (1):
btrfs: fix race when cloning extent buffer during rewind of an old root
Greg Kroah-Hartman (1):
Linux 4.4.263
Gwendal Grignou (1):
platform/chrome: cros_ec_dev - Fix security issue
Jan Kara (3):
ext4: handle error of ext4_setup_system_zone() on remount
ext4: don't allow overlapping system zones
ext4: check journal inode extents more carefully
Jim Lin (1):
usb: gadget: configfs: Fix KASAN use-after-free
Joe Korty (1):
NFSD: Repair misuse of sv_lock in 5.10.16-rt30.
Macpaul Lin (1):
USB: replace hardcode maximum usb string length by definition
Shijie Luo (1):
ext4: fix potential error in ext4_do_update_inode
Thomas Gleixner (2):
x86/ioapic: Ignore IRQ2 again
genirq: Disable interrupts for force threaded handlers
Tyrel Datwyler (1):
PCI: rpadlpar: Fix potential drc_name corruption in store functions
zhangyi (F) (1):
ext4: find old entry again if failed to rename whiteout
next reply other threads:[~2021-03-24 10:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 10:19 Greg Kroah-Hartman [this message]
2021-03-24 10:19 ` Greg Kroah-Hartman
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=161658115316149@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--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
all inboxes | Powered by JetHome®