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 5.4.94
Date: Sat, 30 Jan 2021 15:10:30 +0100 [thread overview]
Message-ID: <16120158304478@kroah.com> (raw)
I'm announcing the release of the 5.4.94 kernel.
All users of the 5.4 kernel series must upgrade.
The updated 5.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-5.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
------------
Documentation/admin-guide/device-mapper/dm-integrity.rst | 6
Makefile | 2
arch/arm64/include/asm/memory.h | 5
arch/arm64/include/asm/pgtable.h | 4
arch/arm64/mm/init.c | 30 --
drivers/gpio/gpio-mvebu.c | 25 -
drivers/hid/wacom_sys.c | 7
drivers/hid/wacom_wac.h | 2
drivers/md/dm-integrity.c | 24 +
fs/cifs/smb2pdu.c | 7
fs/cifs/smb2pdu.h | 14
fs/ext4/inode.c | 2
fs/fs-writeback.c | 36 +-
fs/io_uring.c | 5
fs/xfs/libxfs/xfs_trans_inode.c | 4
include/linux/fs.h | 1
include/trace/events/writeback.h | 1
kernel/futex.c | 219 ++++++---------
kernel/locking/rtmutex.c | 3
kernel/locking/rtmutex_common.h | 3
kernel/trace/ring_buffer.c | 4
mm/slub.c | 4
tools/build/Makefile | 4
tools/objtool/Makefile | 9
tools/perf/Makefile.perf | 4
tools/power/acpi/Makefile.config | 1
tools/scripts/Makefile.include | 10
27 files changed, 210 insertions(+), 226 deletions(-)
Ard Biesheuvel (1):
arm64: mm: use single quantity to represent the PA to VA translation
Baruch Siach (1):
gpio: mvebu: fix pwm .get_state period calculation
Eric Biggers (1):
fs: fix lazytime expiration handling in __writeback_single_inode()
Gaurav Kohli (1):
tracing: Fix race in trace_open and buffer resize call
Greg Kroah-Hartman (1):
Linux 5.4.94
Jan Kara (1):
writeback: Drop I_DIRTY_TIME_EXPIRE
Jason Gerecke (1):
HID: wacom: Correct NULL dereference on AES pen proximity
Jean-Philippe Brucker (1):
tools: Factor HOSTCC, HOSTLD, HOSTAR definitions
Mikulas Patocka (1):
dm integrity: conditionally disable "recalculate" feature
Nicolai Stange (1):
io_uring: Fix current->fs handling in io_sq_wq_submit_work()
Steve French (1):
SMB3.1.1: do not log warning message if server doesn't populate salt
Thomas Gleixner (7):
futex: Ensure the correct return value from futex_lock_pi()
futex: Replace pointless printk in fixup_owner()
futex: Provide and use pi_state_update_owner()
rtmutex: Remove unused argument from rt_mutex_proxy_unlock()
futex: Use pi_state_update_owner() in put_pi_state()
futex: Simplify fixup_pi_state_owner()
futex: Handle faults correctly for PI futexes
Wang Hai (1):
Revert "mm/slub: fix a memory leak in sysfs_slab_add()"
next reply other threads:[~2021-01-30 14:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-30 14:10 Greg Kroah-Hartman [this message]
2021-01-30 14:10 ` Linux 5.4.94 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=16120158304478@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;
as well as URLs for NNTP newsgroup(s).