From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] firewire fixes for v6.7-rc4
Date: Sat, 2 Dec 2023 17:06:48 +0900 [thread overview]
Message-ID: <20231202080648.GA34377@workstation.local> (raw)
Hi Linus,
Please take this pull request for v6.7-rc4 release. It includes a slight
change to fix scarce memory leak.
As I noted in pull request for v6.7[1], Linux FireWire subsystem still
has an issue of unexpected system reboot in AMD Ryzen machine with a
kind of PCI card. Recently I got a help of AMD developer[2] and got some
advices to investigate the mechanism of system reboot, but never catch
its tail yet... I wish to fix it within the development period for v6.8
kernel.
[1] https://lore.kernel.org/lkml/20231105144852.GA165906@workstation.local/
[2] https://lore.kernel.org/lkml/20231128052429.GA25379@workstation.local/
----------------------------------------------------------------
The following changes since commit 2cc14f52aeb78ce3f29677c2de1f06c0e91471ab:
Linux 6.7-rc3 (2023-11-26 19:59:33 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394.git tags/firewire-fixes-6.7-rc4
for you to fetch changes up to 891e0eab32a57fca4d36c5162628eb0bcb1f0edf:
firewire: core: fix possible memory leak in create_units() (2023-11-30 09:16:35 +0900)
----------------------------------------------------------------
firewire fixes for 6.7-rc4
This pull request includes a single patch to fix long-standing issue of
memory leak at failure of device registration for fw_unit. We rarely
encounter the issue, while it should be applied to stable releases, since
it fixes inappropriate API usage.
----------------------------------------------------------------
Yang Yingliang (1):
firewire: core: fix possible memory leak in create_units()
drivers/firewire/core-device.c | 11 ++++-------
1 file changed, 4 insertions(+), 7 deletions(-)
next reply other threads:[~2023-12-02 8:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-02 8:06 Takashi Sakamoto [this message]
2023-12-02 8:32 ` Linux regression tracking (Thorsten Leemhuis)
2023-12-03 1:24 ` 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=20231202080648.GA34377@workstation.local \
--to=o-takashi@sakamocchi.jp \
--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®