mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Thompson <daniel.thompson@linaro.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jason Wessel <jason.wessel@windriver.com>,
	linux-kernel@vger.kernel.org,
	Douglas Anderson <dianders@chromium.org>,
	Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Subject: [GIT PULL] kgdb changes for v6.8
Date: Thu, 18 Jan 2024 14:27:48 +0000	[thread overview]
Message-ID: <20240118142748.GA109045@aspen.lan> (raw)

Hi Linus

Apologies for sending this so late in merge window, especially given as
you will see from the diffstat I can hardly claim to be overworked in
this regard!

Anyhow... the following changes since commit
610a9b8f49fbcf1100716370d3b5f6f884a2835a:

  Linux 6.7-rc8 (2023-12-31 12:51:25 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/danielt/linux.git/ tags/kgdb-6.8-rc1

for you to fetch changes up to 4f41d30cd6dc865c3cbc1a852372321eba6d4e4c:

  kdb: Fix a potential buffer overflow in kdb_local() (2024-01-17 17:19:06 +0000)

----------------------------------------------------------------
kgdb patches for 6.8

The entire changeset for kgdb this cycle is a single two-line change to
remove some deadcode that, had it not been dead, would have called
strncpy() in an unsafe manner.

To be fair there were other modest clean ups were discussed this cycle
but they are not finalized and will have to wait until next time.

Signed-off-by: Daniel Thompson <daniel.thompson@linaro.org>

----------------------------------------------------------------
Christophe JAILLET (1):
      kdb: Fix a potential buffer overflow in kdb_local()

 kernel/debug/kdb/kdb_main.c | 2 --
 1 file changed, 2 deletions(-)

             reply	other threads:[~2024-01-18 14:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-18 14:27 Daniel Thompson [this message]
2024-01-19  2:40 ` 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=20240118142748.GA109045@aspen.lan \
    --to=daniel.thompson@linaro.org \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=dianders@chromium.org \
    --cc=jason.wessel@windriver.com \
    --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

all inboxes | Powered by JetHome®