From: Prithvi <activprithvi@gmail.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: io-uring@vger.kernel.org, brauner@kernel.org, jack@suse.cz,
viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linux.dev, skhan@linuxfoundation.org,
david.hunter.linux@gmail.com, khalid@kernel.org,
syzbot+00e61c43eb5e4740438f@syzkaller.appspotmail.com,
stable@vger.kernel.org
Subject: Re: [PATCH v2] io_uring: fix filename leak in __io_openat_prep()
Date: Thu, 25 Dec 2025 20:48:08 +0530 [thread overview]
Message-ID: <20251225151808.lvpfdwqvcej4vxgm@inspiron> (raw)
In-Reply-To: <176667533028.68806.11770987520631890583.b4-ty@kernel.dk>
On Thu, Dec 25, 2025 at 08:08:50AM -0700, Jens Axboe wrote:
>
> On Thu, 25 Dec 2025 12:58:29 +0530, Prithvi Tambewagh wrote:
> > __io_openat_prep() allocates a struct filename using getname(). However,
> > for the condition of the file being installed in the fixed file table as
> > well as having O_CLOEXEC flag set, the function returns early. At that
> > point, the request doesn't have REQ_F_NEED_CLEANUP flag set. Due to this,
> > the memory for the newly allocated struct filename is not cleaned up,
> > causing a memory leak.
> >
> > [...]
>
> Applied, thanks!
>
> [1/1] io_uring: fix filename leak in __io_openat_prep()
> commit: b14fad555302a2104948feaff70503b64c80ac01
>
> Best regards,
> --
> Jens Axboe
>
>
>
Thank you!
Best Regards,
Prithvi
prev parent reply other threads:[~2025-12-25 15:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-25 7:28 [PATCH v2] io_uring: fix filename leak in __io_openat_prep() Prithvi Tambewagh
2025-12-25 14:58 ` Jens Axboe
2025-12-25 15:08 ` Jens Axboe
2025-12-25 15:18 ` Prithvi [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=20251225151808.lvpfdwqvcej4vxgm@inspiron \
--to=activprithvi@gmail.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=david.hunter.linux@gmail.com \
--cc=io-uring@vger.kernel.org \
--cc=jack@suse.cz \
--cc=khalid@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=syzbot+00e61c43eb5e4740438f@syzkaller.appspotmail.com \
--cc=viro@zeniv.linux.org.uk \
/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