Linux driver-core infrastructure
 help / color / mirror / Atom feed
From: Danilo Krummrich <dakr@kernel.org>
To: Jiacheng Xu <stitch@zju.edu.cn>
Cc: gregkh@linuxfoundation.org, vishal.moola@gmail.com,
	rafael@kernel.org, dakr@kernel.org, akpm@linux-foundation.org,
	driver-core@lists.linux.dev
Subject: Re: [PATCH v3] kobject: fix out-of-bounds access in kobject_action_type()
Date: Thu, 24 Sep 2026 20:46:34 +0200	[thread overview]
Message-ID: <20260924184634.172746-1-dakr@kernel.org> (raw)
In-Reply-To: <20260920053726.22626-1-stitch@zju.edu.cn>

On Sun, 20 Sep 2026 13:37:26 +0800, Jiacheng Xu wrote:
> [PATCH v3] kobject: fix out-of-bounds access in kobject_action_type()

Applied, thanks!

  Branch: driver-core-testing
  Tree:   git://git.kernel.org/pub/scm/linux/kernel/git/driver-core/driver-core.git

[1/1] kobject: fix out-of-bounds access in kobject_action_type()
      commit: d516455c9405

The patch will appear in the next linux-next integration (typically within 24
hours on weekdays).

The patch is in the driver-core-testing branch and will be promoted to
driver-core-next after validation.

      parent reply	other threads:[~2026-09-24 18:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-18  6:26 [PATCH] kobject: fix out-of-bounds read in action parser Jiacheng Xu
2026-08-24 17:32 ` Vishal Moola (Fractile)
2026-08-25  3:54   ` Jiacheng Xu
2026-08-25  3:57   ` [PATCH v2] " Jiacheng Xu
2026-08-25  5:33     ` Greg KH
2026-08-25  6:26       ` [PATCH] " Jiacheng Xu
2026-08-25  6:46         ` Greg KH
2026-08-25  7:05       ` [PATCH v2 RESEND] kobject: fix out-of-bounds access in kobject_action_type() Jiacheng Xu
2026-08-25  7:35         ` Greg KH
2026-08-25 12:12         ` Vishal Moola (Fractile)
2026-09-20  5:37     ` [PATCH v3] " Jiacheng Xu
2026-09-20  6:04       ` Greg KH
2026-09-24 18:46       ` Danilo Krummrich [this message]

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=20260924184634.172746-1-dakr@kernel.org \
    --to=dakr@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=driver-core@lists.linux.dev \
    --cc=gregkh@linuxfoundation.org \
    --cc=rafael@kernel.org \
    --cc=stitch@zju.edu.cn \
    --cc=vishal.moola@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox