linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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.14.279
Date: Sun, 15 May 2022 20:47:03 +0200	[thread overview]
Message-ID: <165264042429201@kroah.com> (raw)

I'm announcing the release of the 4.14.279 kernel.

All users of the 4.14 kernel series must upgrade.

The updated 4.14.y git tree can be found at:
	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.14.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/mips/bmips/setup.c           |    2 
 arch/mips/lantiq/prom.c           |    2 
 arch/mips/pic32/pic32mzda/init.c  |    2 
 arch/mips/ralink/of.c             |    2 
 drivers/block/drbd/drbd_nl.c      |   13 ++--
 drivers/mmc/host/rtsx_pci_sdmmc.c |   30 ++++++----
 drivers/net/can/grcan.c           |   38 ++++++-------
 fs/namespace.c                    |    9 ++-
 include/net/bluetooth/hci_core.h  |    3 +
 include/sound/pcm.h               |    2 
 mm/memory.c                       |    2 
 mm/userfaultfd.c                  |    3 +
 net/bluetooth/hci_core.c          |    6 +-
 sound/core/pcm.c                  |    3 +
 sound/core/pcm_lib.c              |    5 +
 sound/core/pcm_memory.c           |   11 ++-
 sound/core/pcm_native.c           |  110 ++++++++++++++++++++++++++------------
 18 files changed, 163 insertions(+), 82 deletions(-)

Andreas Larsson (2):
      can: grcan: grcan_probe(): fix broken system id check for errata workaround needs
      can: grcan: only use the NAPI poll budget for RX

ChenXiaoSong (1):
      VFS: Fix memory leak caused by concurrently mounting fs with subtype

Greg Kroah-Hartman (1):
      Linux 4.14.279

Itay Iellin (1):
      Bluetooth: Fix the creation of hdev->name

Lee Jones (1):
      block: drbd: drbd_nl: Make conversion to 'enum drbd_ret_code' explicit

Muchun Song (2):
      mm: hugetlb: fix missing cache flush in copy_huge_page_from_user()
      mm: userfaultfd: fix missing cache flush in mcopy_atomic_pte() and __mcopy_atomic()

Nathan Chancellor (1):
      MIPS: Use address-of operator on section symbols

Ricky WU (1):
      mmc: rtsx: add 74 Clocks in power on flow

Takashi Iwai (5):
      ALSA: pcm: Fix races among concurrent hw_params and hw_free calls
      ALSA: pcm: Fix races among concurrent read/write and buffer changes
      ALSA: pcm: Fix races among concurrent prepare and hw_params/hw_free calls
      ALSA: pcm: Fix races among concurrent prealloc proc writes
      ALSA: pcm: Fix potential AB/BA lock with buffer_mutex and mmap_lock


             reply	other threads:[~2022-05-15 18:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-15 18:47 Greg Kroah-Hartman [this message]
2022-05-15 18:47 ` Linux 4.14.279 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=165264042429201@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).