All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Young <sean@mess.org>
To: linux-media@vger.kernel.org
Cc: Rik van Riel <riel@surriel.com>, Sean Young <sean@mess.org>,
	bpf@vger.kernel.org
Subject: [PATCH v2 0/6] Fix locking issues in rc core
Date: Tue,  1 Sep 2026 15:24:50 +0100	[thread overview]
Message-ID: <cover.1788272198.git.sean@mess.org> (raw)

Changes since v1:
 - Fix issue where input device was still leaked
 - Add: Fix race between bpf(BPG_PROG_ATTACH) and device unregister
 - Add: Fix inconsistent locking of keylock

Sean Young (6):
  media: rc: Ensure registered is cleared in error path
  media: rc: Ensure that rc_unregister_device() does not free input
    device
  media: rc: Fix ABBA deadlock by making locks more fine grained
  media: rc: Add missing locking for keymap
  media: rc: Fix race between bpf(BPG_PROG_ATTACH) and device unregister
  media: rc: mce_kbd: Fix inconsistent locking of keylock

 drivers/media/rc/ir-mce_kbd-decoder.c |   5 +-
 drivers/media/rc/rc-ir-raw.c          |  39 ++++---
 drivers/media/rc/rc-main.c            | 147 +++++++++++++++-----------
 include/media/rc-map.h                |   2 -
 4 files changed, 115 insertions(+), 78 deletions(-)

-- 
2.55.0


             reply	other threads:[~2026-09-01 14:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-01 14:24 Sean Young [this message]
2026-09-01 14:24 ` [PATCH v2 1/6] media: rc: Ensure registered is cleared in error path Sean Young
2026-09-01 14:24 ` [PATCH v2 2/6] media: rc: Ensure that rc_unregister_device() does not free input device Sean Young
2026-09-01 14:24 ` [PATCH v2 3/6] media: rc: Fix ABBA deadlock by making locks more fine grained Sean Young
2026-09-01 14:24 ` [PATCH v2 4/6] media: rc: Add missing locking for keymap Sean Young
2026-09-01 14:24 ` [PATCH v2 5/6] media: rc: Fix race between bpf(BPG_PROG_ATTACH) and device unregister Sean Young
2026-09-01 14:24 ` [PATCH v2 6/6] media: rc: mce_kbd: Fix inconsistent locking of keylock Sean Young

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=cover.1788272198.git.sean@mess.org \
    --to=sean@mess.org \
    --cc=bpf@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=riel@surriel.com \
    /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.