public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Arnd Bergmann <arnd@arndb.de>,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] Char/Misc driver fixes for 5.5-rc6
Date: Fri, 10 Jan 2020 22:09:06 +0100	[thread overview]
Message-ID: <20200110210906.GA1871197@kroah.com> (raw)

The following changes since commit c79f46a282390e0f5b306007bf7b11a46d529538:

  Linux 5.5-rc5 (2020-01-05 14:23:27 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git tags/char-misc-5.5-rc6

for you to fetch changes up to 68faa679b8be1a74e6663c21c3a9d25d32f1c079:

  chardev: Avoid potential use-after-free in 'chrdev_open()' (2020-01-06 20:10:26 +0100)

----------------------------------------------------------------
Char/Misc patch for 5.5-rc6

Here is a single fix, for the chrdev core, for 5.5-rc6

There's been a long-standing race condition triggered by syzbot, and
occasionally real people, in the chrdev open() path.  Will finally took
the time to track it down and fix it for real before the holidays.

Here's that one patch, it's been in linux-next for a while with no
reported issues and it does fix the reported problem.

Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

----------------------------------------------------------------
Will Deacon (1):
      chardev: Avoid potential use-after-free in 'chrdev_open()'

 fs/char_dev.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

             reply	other threads:[~2020-01-10 21:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-10 21:09 Greg KH [this message]
2020-01-11 14:45 ` [GIT PULL] Char/Misc driver fixes for 5.5-rc6 pr-tracker-bot

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=20200110210906.GA1871197@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=linux-kernel@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