Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Vegard Nossum <vegard.nossum@oracle.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	stable@vger.kernel.org, pavel@denx.de, cengiz.can@canonical.com,
	mheyne@amazon.de, mngyadam@amazon.com, kuntal.nayak@broadcom.com,
	ajay.kaher@broadcom.com, zsm@chromium.org,
	dan.carpenter@linaro.org, shivani.agarwal@broadcom.com,
	Zhihao Cheng <chengzhihao1@huawei.com>,
	Eric Biggers <ebiggers@kernel.org>,
	Eric Biggers <ebiggers@google.com>,
	Richard Weinberger <richard@nod.at>
Subject: Re: [PATCH RFC 6.6.y 01/15] ubifs: ubifs_symlink: Fix memleak of inode->i_link in error path
Date: Fri, 4 Oct 2024 20:45:49 -0400	[thread overview]
Message-ID: <ZwCMPZd_P8kNxaIn@sashalap> (raw)
In-Reply-To: <20241002150606.11385-2-vegard.nossum@oracle.com>

On Wed, Oct 02, 2024 at 05:05:52PM +0200, Vegard Nossum wrote:
>From: Zhihao Cheng <chengzhihao1@huawei.com>
>
>[ Upstream commit 6379b44cdcd67f5f5d986b73953e99700591edfa ]

This landed as a duplicate in the upstream tree:

1e022216dcd2 ("ubifs: ubifs_symlink: Fix memleak of inode->i_link in error path")
6379b44cdcd6 ("ubifs: ubifs_symlink: Fix memleak of inode->i_link in error path")

We've backported 1e022216dcd2, and so the issue should be addressed.

-- 
Thanks,
Sasha

  parent reply	other threads:[~2024-10-05  0:45 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-02 15:05 [PATCH RFC 6.6.y 00/15] Some missing CVE fixes Vegard Nossum
2024-10-02 15:05 ` [PATCH RFC 6.6.y 01/15] ubifs: ubifs_symlink: Fix memleak of inode->i_link in error path Vegard Nossum
2024-10-02 16:26   ` Dan Carpenter
2024-10-02 16:29     ` Dan Carpenter
2024-10-05  0:45   ` Sasha Levin [this message]
2024-10-02 15:05 ` [PATCH RFC 6.6.y 02/15] media: usbtv: Remove useless locks in usbtv_video_free() Vegard Nossum
2024-10-02 15:05 ` [PATCH RFC 6.6.y 03/15] Bluetooth: hci_sock: Fix not validating setsockopt user input Vegard Nossum
2024-10-02 15:05 ` [PATCH RFC 6.6.y 04/15] Bluetooth: ISO: " Vegard Nossum
2024-10-02 15:05 ` [PATCH RFC 6.6.y 05/15] Bluetooth: L2CAP: " Vegard Nossum
2024-10-02 15:05 ` [PATCH RFC 6.6.y 06/15] netfilter: nf_tables: fix memleak in map from abort path Vegard Nossum
2024-10-02 15:05 ` [PATCH RFC 6.6.y 07/15] netfilter: nf_tables: restore set elements when delete set fails Vegard Nossum
2024-10-02 15:05 ` [PATCH RFC 6.6.y 08/15] net: dsa: fix netdev_priv() dereference before check on non-DSA netdevice events Vegard Nossum
2024-10-02 15:06 ` [PATCH RFC 6.6.y 09/15] iommufd: Fix protection fault in iommufd_test_syz_conv_iova Vegard Nossum
2024-10-02 15:16   ` Jason Gunthorpe
2024-10-02 15:06 ` [PATCH RFC 6.6.y 10/15] drm/bridge: adv7511: fix crash on irq during probe Vegard Nossum
2024-10-02 15:12 ` [PATCH RFC 6.6.y 11/15] efi/unaccepted: touch soft lockup during memory accept Vegard Nossum
2024-10-02 15:12   ` [PATCH RFC 6.6.y 12/15] platform/x86: think-lmi: Fix password opcode ordering for workstations Vegard Nossum
2024-10-04  1:00     ` Mark Pearson
2024-10-02 15:12   ` [PATCH RFC 6.6.y 13/15] null_blk: Remove usage of the deprecated ida_simple_xx() API Vegard Nossum
2024-10-02 15:12   ` [PATCH RFC 6.6.y 14/15] null_blk: fix null-ptr-dereference while configuring 'power' and 'submit_queues' Vegard Nossum
2024-10-02 15:12   ` [PATCH RFC 6.6.y 15/15] net: stmmac: move the EST lock to struct stmmac_priv Vegard Nossum
2024-10-02 15:26 ` [PATCH RFC 6.6.y 00/15] Some missing CVE fixes Jens Axboe
2024-10-02 15:46   ` Vegard Nossum
2024-10-02 15:49     ` Jens Axboe
2024-10-08 11:19     ` Pavel Machek
2024-10-08 11:24       ` Greg Kroah-Hartman
2024-10-08 11:40         ` Pavel Machek
2024-10-08 11:51           ` Greg Kroah-Hartman
2024-10-02 15:50   ` Dan Carpenter
2024-10-02 15:54     ` Jens Axboe
2024-10-08 11:16   ` Pavel Machek
2024-10-08 11:24     ` Greg Kroah-Hartman
2024-10-08 11:35       ` Pavel Machek
2024-10-08 11:44         ` Greg Kroah-Hartman
2024-10-08 11:56           ` Christian Heusel
2024-10-08 12:33           ` Pavel Machek
2024-10-08 13:02             ` Greg Kroah-Hartman
2024-10-02 19:43 ` Pablo Neira Ayuso
2024-10-08 10:32 ` Greg Kroah-Hartman

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=ZwCMPZd_P8kNxaIn@sashalap \
    --to=sashal@kernel.org \
    --cc=ajay.kaher@broadcom.com \
    --cc=cengiz.can@canonical.com \
    --cc=chengzhihao1@huawei.com \
    --cc=dan.carpenter@linaro.org \
    --cc=ebiggers@google.com \
    --cc=ebiggers@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kuntal.nayak@broadcom.com \
    --cc=mheyne@amazon.de \
    --cc=mngyadam@amazon.com \
    --cc=pavel@denx.de \
    --cc=richard@nod.at \
    --cc=shivani.agarwal@broadcom.com \
    --cc=stable@vger.kernel.org \
    --cc=vegard.nossum@oracle.com \
    --cc=zsm@chromium.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