From: patchwork-bot+f2fs@kernel.org
To: Eric Biggers <ebiggers@kernel.org>
Cc: jaegeuk@kernel.org, glider@google.com, stable@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix information leak in f2fs_move_inline_dirents()
Date: Mon, 30 Jan 2023 23:00:17 +0000 [thread overview]
Message-ID: <167511961786.12751.10866509734206630885.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230123070414.138052-1-ebiggers@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Sun, 22 Jan 2023 23:04:14 -0800 you wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> When converting an inline directory to a regular one, f2fs is leaking
> uninitialized memory to disk because it doesn't initialize the entire
> directory block. Fix this by zero-initializing the block.
>
> This bug was introduced by commit 4ec17d688d74 ("f2fs: avoid unneeded
> initializing when converting inline dentry"), which didn't consider the
> security implications of leaking uninitialized memory to disk.
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix information leak in f2fs_move_inline_dirents()
https://git.kernel.org/jaegeuk/f2fs/c/638ce5437867
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+f2fs@kernel.org
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net, jaegeuk@kernel.org,
chao@kernel.org, glider@google.com, stable@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix information leak in f2fs_move_inline_dirents()
Date: Mon, 30 Jan 2023 23:00:17 +0000 [thread overview]
Message-ID: <167511961786.12751.10866509734206630885.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230123070414.138052-1-ebiggers@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Sun, 22 Jan 2023 23:04:14 -0800 you wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> When converting an inline directory to a regular one, f2fs is leaking
> uninitialized memory to disk because it doesn't initialize the entire
> directory block. Fix this by zero-initializing the block.
>
> This bug was introduced by commit 4ec17d688d74 ("f2fs: avoid unneeded
> initializing when converting inline dentry"), which didn't consider the
> security implications of leaking uninitialized memory to disk.
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix information leak in f2fs_move_inline_dirents()
https://git.kernel.org/jaegeuk/f2fs/c/638ce5437867
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-01-30 23:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 7:04 [f2fs-dev] [PATCH] f2fs: fix information leak in f2fs_move_inline_dirents() Eric Biggers
2023-01-23 7:04 ` Eric Biggers
2023-01-23 8:58 ` [f2fs-dev] " Alexander Potapenko via Linux-f2fs-devel
2023-01-23 8:58 ` Alexander Potapenko
2023-01-23 18:19 ` [f2fs-dev] " Eric Biggers
2023-01-23 18:19 ` Eric Biggers
2023-01-25 10:10 ` [f2fs-dev] " Alexander Potapenko via Linux-f2fs-devel
2023-01-25 10:10 ` Alexander Potapenko
2023-01-29 9:57 ` [f2fs-dev] " Chao Yu
2023-01-29 9:57 ` Chao Yu
2023-01-30 23:00 ` patchwork-bot+f2fs [this message]
2023-01-30 23:00 ` [f2fs-dev] " patchwork-bot+f2fs
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=167511961786.12751.10866509734206630885.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=ebiggers@kernel.org \
--cc=glider@google.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.