All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Sven Van Asbroeck <thesven73@gmail.com>,
	Tejun Heo <tj@kernel.org>, Lai Jiangshan <jiangshanlai@gmail.com>,
	Sebastian Reichel <sre@kernel.org>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Kees Cook <keescook@chromium.org>
Subject: [GIT PULL] auxdisplay for v5.0-rc7
Date: Fri, 15 Feb 2019 20:22:26 +0100	[thread overview]
Message-ID: <20190215192226.GA24834@gmail.com> (raw)

Hi Linus,

Please pull this small fix for a potential user-after-free on module
unload.

It has been sitting in -next for some days.

Cheers,
Miguel

The following changes since commit 8834f5600cf3c8db365e18a3d5cac2c2780c81e5:

  Linux 5.0-rc5 (2019-02-03 13:48:04 -0800)

are available in the Git repository at:

  https://github.com/ojeda/linux.git tags/auxdisplay-for-linus-v5.0-rc7

for you to fetch changes up to 69ef9bc54715fb1cb7786ada15774e469e822209:

  auxdisplay: ht16k33: fix potential user-after-free on module unload (2019-02-15 19:48:39 +0100)

----------------------------------------------------------------
auxdisplay:

  - ht16k33: fix potential user-after-free on module unload
    Reported by Sven Van Asbroeck

----------------------------------------------------------------
Miguel Ojeda (1):
      auxdisplay: ht16k33: fix potential user-after-free on module unload

 drivers/auxdisplay/ht16k33.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

             reply	other threads:[~2019-02-15 19:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-15 19:22 Miguel Ojeda [this message]
2019-02-17  1:50 ` [GIT PULL] auxdisplay for v5.0-rc7 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=20190215192226.GA24834@gmail.com \
    --to=miguel.ojeda.sandonis@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jiangshanlai@gmail.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sre@kernel.org \
    --cc=thesven73@gmail.com \
    --cc=tj@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.