From: Eric Biggers <ebiggers@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: patchwork-bot+f2fs@kernel.org, linux-fscrypt@vger.kernel.org,
aalbersh@redhat.com, linux-f2fs-devel@lists.sourceforge.net,
linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-ext4@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 00/11] fsverity: support for non-4K pages
Date: Tue, 28 Feb 2023 01:30:39 +0000 [thread overview]
Message-ID: <Y/1ZP9pc1Zw9xh/L@gmail.com> (raw)
In-Reply-To: <167754611492.27916.393758892204411776.git-patchwork-notify@kernel.org>
On Tue, Feb 28, 2023 at 01:01:54AM +0000, patchwork-bot+f2fs@kernel.org wrote:
> Hello:
>
> This series was applied to jaegeuk/f2fs.git (dev)
> by Eric Biggers <ebiggers@google.com>:
>
> On Fri, 23 Dec 2022 12:36:27 -0800 you wrote:
> > [This patchset applies to mainline + some fsverity cleanups I sent out
> > recently. You can get everything from tag "fsverity-non4k-v2" of
> > https://git.kernel.org/pub/scm/fs/fscrypt/fscrypt.git ]
> >
> > Currently, filesystems (ext4, f2fs, and btrfs) only support fsverity
> > when the Merkle tree block size, filesystem block size, and page size
> > are all the same. In practice that means 4K, since increasing the page
> > size, e.g. to 16K, forces the Merkle tree block size and filesystem
> > block size to be increased accordingly. That can be impractical; for
> > one, users want the same file signatures to work on all systems.
> >
> > [...]
>
> Here is the summary with links:
> - [f2fs-dev,v2,01/11] fsverity: use unsigned long for level_start
> https://git.kernel.org/jaegeuk/f2fs/c/284d5db5f99e
> - [f2fs-dev,v2,02/11] fsverity: simplify Merkle tree readahead size calculation
> https://git.kernel.org/jaegeuk/f2fs/c/9098f36b739d
> - [f2fs-dev,v2,03/11] fsverity: store log2(digest_size) precomputed
> https://git.kernel.org/jaegeuk/f2fs/c/579a12f78d88
> - [f2fs-dev,v2,04/11] fsverity: use EFBIG for file too large to enable verity
> https://git.kernel.org/jaegeuk/f2fs/c/55eed69cc8fd
> - [f2fs-dev,v2,05/11] fsverity: replace fsverity_hash_page() with fsverity_hash_block()
> https://git.kernel.org/jaegeuk/f2fs/c/f45555bf23cf
> - [f2fs-dev,v2,06/11] fsverity: support verification with tree block size < PAGE_SIZE
> https://git.kernel.org/jaegeuk/f2fs/c/5306892a50bf
> - [f2fs-dev,v2,07/11] fsverity: support enabling with tree block size < PAGE_SIZE
> https://git.kernel.org/jaegeuk/f2fs/c/56124d6c87fd
> - [f2fs-dev,v2,08/11] ext4: simplify ext4_readpage_limit()
> https://git.kernel.org/jaegeuk/f2fs/c/5e122148a3d5
> - [f2fs-dev,v2,09/11] f2fs: simplify f2fs_readpage_limit()
> https://git.kernel.org/jaegeuk/f2fs/c/feb0576a361a
> - [f2fs-dev,v2,10/11] fs/buffer.c: support fsverity in block_read_full_folio()
> https://git.kernel.org/jaegeuk/f2fs/c/4fa512ce7051
> - [f2fs-dev,v2,11/11] ext4: allow verity with fs block size < PAGE_SIZE
> https://git.kernel.org/jaegeuk/f2fs/c/db85d14dc5c5
>
> You are awesome, thank you!
> --
> Deet-doot-dot, I am a bot.
> https://korg.docs.kernel.org/patchwork/pwbot.html
>
These commits reached the f2fs tree through mainline, not through being applied
to the f2fs tree. So this email shouldn't have been sent. Jaegeuk, can you
look into fixing the configuration of the f2fs patchwork bot to prevent this?
- Eric
WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers <ebiggers@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: patchwork-bot+f2fs@kernel.org, aalbersh@redhat.com,
linux-f2fs-devel@lists.sourceforge.net,
linux-xfs@vger.kernel.org, linux-fscrypt@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-btrfs@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH v2 00/11] fsverity: support for non-4K pages
Date: Tue, 28 Feb 2023 01:30:39 +0000 [thread overview]
Message-ID: <Y/1ZP9pc1Zw9xh/L@gmail.com> (raw)
In-Reply-To: <167754611492.27916.393758892204411776.git-patchwork-notify@kernel.org>
On Tue, Feb 28, 2023 at 01:01:54AM +0000, patchwork-bot+f2fs@kernel.org wrote:
> Hello:
>
> This series was applied to jaegeuk/f2fs.git (dev)
> by Eric Biggers <ebiggers@google.com>:
>
> On Fri, 23 Dec 2022 12:36:27 -0800 you wrote:
> > [This patchset applies to mainline + some fsverity cleanups I sent out
> > recently. You can get everything from tag "fsverity-non4k-v2" of
> > https://git.kernel.org/pub/scm/fs/fscrypt/fscrypt.git ]
> >
> > Currently, filesystems (ext4, f2fs, and btrfs) only support fsverity
> > when the Merkle tree block size, filesystem block size, and page size
> > are all the same. In practice that means 4K, since increasing the page
> > size, e.g. to 16K, forces the Merkle tree block size and filesystem
> > block size to be increased accordingly. That can be impractical; for
> > one, users want the same file signatures to work on all systems.
> >
> > [...]
>
> Here is the summary with links:
> - [f2fs-dev,v2,01/11] fsverity: use unsigned long for level_start
> https://git.kernel.org/jaegeuk/f2fs/c/284d5db5f99e
> - [f2fs-dev,v2,02/11] fsverity: simplify Merkle tree readahead size calculation
> https://git.kernel.org/jaegeuk/f2fs/c/9098f36b739d
> - [f2fs-dev,v2,03/11] fsverity: store log2(digest_size) precomputed
> https://git.kernel.org/jaegeuk/f2fs/c/579a12f78d88
> - [f2fs-dev,v2,04/11] fsverity: use EFBIG for file too large to enable verity
> https://git.kernel.org/jaegeuk/f2fs/c/55eed69cc8fd
> - [f2fs-dev,v2,05/11] fsverity: replace fsverity_hash_page() with fsverity_hash_block()
> https://git.kernel.org/jaegeuk/f2fs/c/f45555bf23cf
> - [f2fs-dev,v2,06/11] fsverity: support verification with tree block size < PAGE_SIZE
> https://git.kernel.org/jaegeuk/f2fs/c/5306892a50bf
> - [f2fs-dev,v2,07/11] fsverity: support enabling with tree block size < PAGE_SIZE
> https://git.kernel.org/jaegeuk/f2fs/c/56124d6c87fd
> - [f2fs-dev,v2,08/11] ext4: simplify ext4_readpage_limit()
> https://git.kernel.org/jaegeuk/f2fs/c/5e122148a3d5
> - [f2fs-dev,v2,09/11] f2fs: simplify f2fs_readpage_limit()
> https://git.kernel.org/jaegeuk/f2fs/c/feb0576a361a
> - [f2fs-dev,v2,10/11] fs/buffer.c: support fsverity in block_read_full_folio()
> https://git.kernel.org/jaegeuk/f2fs/c/4fa512ce7051
> - [f2fs-dev,v2,11/11] ext4: allow verity with fs block size < PAGE_SIZE
> https://git.kernel.org/jaegeuk/f2fs/c/db85d14dc5c5
>
> You are awesome, thank you!
> --
> Deet-doot-dot, I am a bot.
> https://korg.docs.kernel.org/patchwork/pwbot.html
>
These commits reached the f2fs tree through mainline, not through being applied
to the f2fs tree. So this email shouldn't have been sent. Jaegeuk, can you
look into fixing the configuration of the f2fs patchwork bot to prevent this?
- Eric
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2023-02-28 1:30 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 20:36 [PATCH v2 00/11] fsverity: support for non-4K pages Eric Biggers
2022-12-23 20:36 ` [f2fs-dev] " Eric Biggers
2022-12-23 20:36 ` [PATCH v2 01/11] fsverity: use unsigned long for level_start Eric Biggers
2022-12-23 20:36 ` [f2fs-dev] " Eric Biggers
2022-12-23 20:36 ` [PATCH v2 02/11] fsverity: simplify Merkle tree readahead size calculation Eric Biggers
2022-12-23 20:36 ` [f2fs-dev] " Eric Biggers
2022-12-23 20:36 ` [PATCH v2 03/11] fsverity: store log2(digest_size) precomputed Eric Biggers
2022-12-23 20:36 ` [f2fs-dev] " Eric Biggers
2022-12-23 20:36 ` [PATCH v2 04/11] fsverity: use EFBIG for file too large to enable verity Eric Biggers
2022-12-23 20:36 ` [f2fs-dev] " Eric Biggers
2022-12-23 20:36 ` [PATCH v2 05/11] fsverity: replace fsverity_hash_page() with fsverity_hash_block() Eric Biggers
2022-12-23 20:36 ` [f2fs-dev] " Eric Biggers
2022-12-23 20:36 ` [PATCH v2 06/11] fsverity: support verification with tree block size < PAGE_SIZE Eric Biggers
2022-12-23 20:36 ` [f2fs-dev] " Eric Biggers
2022-12-23 20:36 ` [PATCH v2 07/11] fsverity: support enabling " Eric Biggers
2022-12-23 20:36 ` [f2fs-dev] " Eric Biggers
2022-12-23 20:36 ` [PATCH v2 08/11] ext4: simplify ext4_readpage_limit() Eric Biggers
2022-12-23 20:36 ` [f2fs-dev] " Eric Biggers
2022-12-23 20:36 ` [PATCH v2 09/11] f2fs: simplify f2fs_readpage_limit() Eric Biggers
2022-12-23 20:36 ` [f2fs-dev] " Eric Biggers
2022-12-23 20:36 ` [PATCH v2 10/11] fs/buffer.c: support fsverity in block_read_full_folio() Eric Biggers
2022-12-23 20:36 ` [f2fs-dev] " Eric Biggers
2023-01-10 2:37 ` Andrew Morton
2023-01-10 2:37 ` [f2fs-dev] " Andrew Morton
2023-01-10 3:05 ` Eric Biggers
2023-01-10 3:05 ` [f2fs-dev] " Eric Biggers
2023-01-20 19:56 ` Eric Biggers
2023-01-20 19:56 ` [f2fs-dev] " Eric Biggers
2023-01-21 6:39 ` Christoph Hellwig
2023-01-21 6:39 ` [f2fs-dev] " Christoph Hellwig
2022-12-23 20:36 ` [PATCH v2 11/11] ext4: allow verity with fs block size < PAGE_SIZE Eric Biggers
2022-12-23 20:36 ` [f2fs-dev] " Eric Biggers
2023-01-04 6:38 ` [PATCH v2 00/11] fsverity: support for non-4K pages Ojaswin Mujoo
2023-01-04 6:38 ` [f2fs-dev] " Ojaswin Mujoo via Linux-f2fs-devel
2023-01-04 7:25 ` Eric Biggers
2023-01-04 7:25 ` [f2fs-dev] " Eric Biggers
2023-01-05 11:24 ` Ojaswin Mujoo
2023-01-05 11:24 ` [f2fs-dev] " Ojaswin Mujoo via Linux-f2fs-devel
2023-01-09 17:38 ` Eric Biggers
2023-01-09 17:38 ` [f2fs-dev] " Eric Biggers
2023-01-09 19:34 ` Andrey Albershteyn
2023-01-09 19:34 ` [f2fs-dev] " Andrey Albershteyn
2023-01-10 3:10 ` Eric Biggers
2023-01-10 3:10 ` [f2fs-dev] " Eric Biggers
2023-02-03 22:01 ` Eric Biggers
2023-02-03 22:01 ` [f2fs-dev] " Eric Biggers
2023-02-28 1:01 ` patchwork-bot+f2fs
2023-02-28 1:01 ` patchwork-bot+f2fs
2023-02-28 1:30 ` Eric Biggers [this message]
2023-02-28 1:30 ` Eric Biggers
2023-02-28 3:53 ` Jaegeuk Kim
2023-02-28 3:53 ` [f2fs-dev] " Jaegeuk Kim
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=Y/1ZP9pc1Zw9xh/L@gmail.com \
--to=ebiggers@kernel.org \
--cc=aalbersh@redhat.com \
--cc=jaegeuk@kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=patchwork-bot+f2fs@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.