public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Chenyuan Yang <chenyuan0y@gmail.com>
Cc: linux-mtd@lists.infradead.org, richard@nod.at,
	miquel.raynal@bootlin.com, Zhihao Cheng <chengzhihao1@huawei.com>,
	vigneshr@ti.com, linux-kernel@vger.kernel.org,
	syzkaller@googlegroups.com, Zijie Zhao <zzjas98@gmail.com>,
	rafael@kernel.org, akpm@linux-foundation.org
Subject: Re: [Linux Kernel Bug] memory leak in ubi_attach
Date: Fri, 11 Oct 2024 07:35:03 +0200	[thread overview]
Message-ID: <2024101141-mooned-crestless-8ce2@gregkh> (raw)
In-Reply-To: <CALGdzuoWvy5WvpttC1pab309kZ9cUyfT5O7JB8VjsqwU2HD0Xg@mail.gmail.com>

On Thu, Oct 10, 2024 at 08:23:22PM -0500, Chenyuan Yang wrote:
> Dear Linux Kernel Developers for UBI and Kernel Object,
> 
> I am writing to inquire if there have been any updates regarding this
> memory leak issue. This issue remains reproducible on the latest
> Linux version (6.12-rc2, commit
> 8cf0b93919e13d1e8d4466eb4080a4c4d9d66d7b).
> 
> Thank you for your attention to this matter.

Can you create a patch for this as you seem to have a good reproducer
for the problem.

thanks,

greg k-h

  reply	other threads:[~2024-10-11  5:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-23  3:53 [Linux Kernel Bug] memory leak in ubi_attach Chenyuan Yang
2024-01-23  4:55 ` Zhihao Cheng
     [not found]   ` <CALGdzuryBbCqGAhox9ZWaQHD5dSQNApfGmCP+rYZ7O4MCRH+rw@mail.gmail.com>
2024-01-24 12:44     ` Zhihao Cheng
2024-01-24 14:41       ` Chenyuan Yang
2024-01-29 11:51         ` Zhihao Cheng
2024-10-11  1:23           ` Chenyuan Yang
2024-10-11  5:35             ` Greg KH [this message]
2024-10-15  3:41             ` Ryder Wang
2024-10-15  6:54               ` gregkh
     [not found] <PH0PR11MB7496D8FBFAC72061A9C5F07CD1242@PH0PR11MB7496.namprd11.prod.outlook.com>
2024-11-15 14:11 ` syzbot

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=2024101141-mooned-crestless-8ce2@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=chengzhihao1@huawei.com \
    --cc=chenyuan0y@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=rafael@kernel.org \
    --cc=richard@nod.at \
    --cc=syzkaller@googlegroups.com \
    --cc=vigneshr@ti.com \
    --cc=zzjas98@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