All of lore.kernel.org
 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.4.280
Date: Tue, 10 Aug 2021 18:11:19 +0200	[thread overview]
Message-ID: <1628611879145216@kroah.com> (raw)

I'm announcing the release of the 4.4.280 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 
 include/linux/rcupdate.h        |    4 
 kernel/futex.c                  |  245 ++++++++++++++++++++++++++--------------
 kernel/locking/rtmutex.c        |  185 ++++++++++++++++--------------
 kernel/locking/rtmutex_common.h |    2 
 5 files changed, 263 insertions(+), 175 deletions(-)

Anna-Maria Gleixner (1):
      rcu: Update documentation of rcu_read_unlock()

Greg Kroah-Hartman (1):
      Linux 4.4.280

Mike Galbraith (1):
      futex: Handle transient "ownerless" rtmutex state correctly

Peter Zijlstra (6):
      futex: Cleanup refcounting
      futex,rt_mutex: Introduce rt_mutex_init_waiter()
      futex: Pull rt_mutex_futex_unlock() out from under hb->lock
      futex: Rework futex_lock_pi() to use rt_mutex_*_proxy_lock()
      futex: Futex_unlock_pi() determinism
      futex,rt_mutex: Fix rt_mutex_cleanup_proxy_lock()

Thomas Gleixner (3):
      futex: Rename free_pi_state() to put_pi_state()
      rtmutex: Make wait_lock irq safe
      futex: Avoid freeing an active timer


             reply	other threads:[~2021-08-10 16:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-10 16:11 Greg Kroah-Hartman [this message]
2021-08-10 16:11 ` Linux 4.4.280 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=1628611879145216@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.