Compression option in inode should not be changed after they have
been used, however, it may happen in below race case:
Thread AThread B
- f2fs_ioc_set_compress_option
- check f2fs_is_mmap_file()
- check get_dirty_pages()
- check F2FS_HAS_BLOCKS()
On 2023/7/6 1:30, Jaegeuk Kim wrote:
On 07/04, Chao Yu wrote:
On 2023/7/4 18:53, Jaegeuk Kim wrote:
On 07/03, Chao Yu wrote:
On 2023/6/15 0:10, Jaegeuk Kim wrote:
If there're huge # of small discards, this will increase checkpoint latency
insanely. Let's issue small discards only by trim.
Si
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Andrew Morton :
On Fri, 19 May 2023 11:35:09 +0200 you wrote:
> Move the ki_pos update down a bit to prepare for a better common
> helper that invalidates pages based of an iocb.
>
> Signed-off-by: Christoph Hellwig
> ---
> fs/iomap/d
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jens Axboe :
On Mon, 24 Apr 2023 07:49:10 +0200 you wrote:
> buffer_check_dirty_writeback is only used by the block device aops,
> remove the export.
>
> Signed-off-by: Christoph Hellwig
> ---
> fs/buffer.c | 1 -
> 1 file changed, 1
Hello:
The following patches were marked "accepted", because they were applied to
jaegeuk/f2fs.git (dev):
Series: [f2fs-dev,01/12] backing_dev: remove current->backing_dev_info
Submitter: Christoph Hellwig
Committer: Andrew Morton
Patchwork: https://patchwork.kernel.org/project/f2fs/list/
Hello:
This pull request was applied to jaegeuk/f2fs.git (dev)
by Linus Torvalds :
On Wed, 5 Jul 2023 10:54:07 -0700 you wrote:
> Hi Linus,
>
> Could you please consider this pull request?
>
> Thank you.
>
> The following changes since commit ac9a78681b921877518763ba0e89202254349d1b:
>
> [...
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Christian Brauner :
On Thu, 1 Jun 2023 12:58:20 +0200 you wrote:
> Hello,
>
> this patch set fixes a problem with cross directory renames originally
> reported
> in [1]. To quickly sum it up some filesystems (so far we know at least a
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jens Axboe :
On Sat, 20 May 2023 01:00:38 +0100 you wrote:
> Provide a splice_read stub for f2fs. This does some checks and tracing
> before calling filemap_splice_read() and will update the iostats
> afterwards. Direct I/O is handled b
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jens Axboe :
On Mon, 22 May 2023 14:50:06 +0100 you wrote:
> Provide a splice_read wrapper for f2fs. This does some checks and tracing
> before calling filemap_splice_read() and will update the iostats
> afterwards. Direct I/O is handle
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Andrew Morton :
On Thu, 1 Jun 2023 16:58:53 +0200 you wrote:
> The last user of current->backing_dev_info disappeared in commit
> b9b1335e6403 ("remove bdi_congested() and wb_congested() and related
> functions"). Remove the field and
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jens Axboe :
On Thu, 8 Jun 2023 13:02:29 +0200 you wrote:
> For whole devices ->open is called for each open, but for partitions it
> is only called on the first open of a partition, e.g.:
>
> open("/dev/vdb", ...)
> open("/dev/vdb
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Eric Biggers :
On Mon, 15 May 2023 22:23:06 -0700 you wrote:
> From: Eric Biggers
>
> The "ahash" API, like the other scatterlist-based crypto APIs such as
> "skcipher", comes with some well-known limitations. First, it can't
> easily
On Thu, 2023-07-06 at 08:19 +0900, Damien Le Moal wrote:
> On 7/6/23 03:58, Jeff Layton wrote:
> > A rename potentially involves updating 4 different inode timestamps. Add
> > a function that handles the details sanely, and convert the libfs.c
> > callers to use it.
> >
> > Signed-off-by: Jeff Lay
On 7/6/23 03:58, Jeff Layton wrote:
> Now that everything in-tree is converted to use the accessor functions,
> rename the i_ctime field in the inode to discourage direct access.
>
> Signed-off-by: Jeff Layton
Looks OK to me.
Reviewed-by: Damien Le Moal
--
Damien Le Moal
Western Digital Rese
On 7/6/23 03:58, Jeff Layton wrote:
> A rename potentially involves updating 4 different inode timestamps. Add
> a function that handles the details sanely, and convert the libfs.c
> callers to use it.
>
> Signed-off-by: Jeff Layton
> ---
> fs/libfs.c | 36 +++
On 7/6/23 03:58, Jeff Layton wrote:
> struct timespec64 has unused bits in the tv_nsec field that can be used
> for other purposes. In future patches, we're going to change how the
> inode->i_ctime is accessed in certain inodes in order to make use of
> them. In order to do that safely though, we'l
e:
If you sent me an Acked-by or Reviewed-by in the previous set, then I
tried to keep it on the patch here, since the respun patches are mostly
just renaming stuff from v1. Let me know if I've missed any.
I've also pushed the pile to my tree as this tag:
https://git.kernel.org/pub/sc
From: Eric Biggers
Since CONFIG_FS_VERITY is a bool, not a tristate, fs/verity/ can only be
builtin or absent entirely; it can't be a loadable module. Therefore,
the error code that gets returned from the fsverity_init() initcall is
never used. If any part of the initcall does fail, which shoul
This series simplifies handling of errors during the fsverity_init()
initcall, and moves the sysctl registration out of signature.c so that
it is not unnecessarily tied to the builtin signature feature.
Eric Biggers (2):
fsverity: simplify handling of errors during initcall
fsverity: move sysc
From: Eric Biggers
Currently the registration of the fsverity sysctls happens in
signature.c, which couples it to CONFIG_FS_VERITY_BUILTIN_SIGNATURES.
This makes it hard to add new sysctls unrelated to builtin signatures.
Also, some users have started checking whether the directory
/proc/sys/fs
The pull request you sent on Wed, 5 Jul 2023 10:54:07 -0700:
> git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git
> tags/f2fs-for-6.5-rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/73a3fcdaa73200e38e38f7e8a32c9b901c5b95b5
Thank you!
--
Deet-doot-dot
In later patches, we're going to change how the inode's ctime field is
used. Switch to using accessor functions instead of raw accesses of
inode->i_ctime.
Signed-off-by: Jeff Layton
---
fs/f2fs/dir.c | 8
fs/f2fs/f2fs.h | 4 +++-
fs/f2fs/file.c | 20 ++--
Now that everything in-tree is converted to use the accessor functions,
rename the i_ctime field in the inode to discourage direct access.
Signed-off-by: Jeff Layton
---
include/linux/fs.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/include/linux/fs.h b/include/linu
struct timespec64 has unused bits in the tv_nsec field that can be used
for other purposes. In future patches, we're going to change how the
inode->i_ctime is accessed in certain inodes in order to make use of
them. In order to do that safely though, we'll need to eradicate raw
accesses of the inod
A rename potentially involves updating 4 different inode timestamps. Add
a function that handles the details sanely, and convert the libfs.c
callers to use it.
Signed-off-by: Jeff Layton
---
fs/libfs.c | 36 +++-
include/linux/fs.h | 2 ++
2 files changed
v2:
- prepend patches to add missing ctime updates
- add simple_rename_timestamp helper function
- rename ctime accessor functions as inode_get_ctime/inode_set_ctime_*
- drop individual inode_ctime_set_{sec,nsec} helpers
I've been working on a patchset to change how the inode->i_ctime is
accessed
Hi Linus,
Could you please consider this pull request?
Thank you.
The following changes since commit ac9a78681b921877518763ba0e89202254349d1b:
Linux 6.4-rc1 (2023-05-07 13:34:35 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git
On 07/04, Chao Yu wrote:
> On 2023/7/4 18:53, Jaegeuk Kim wrote:
> > On 07/03, Chao Yu wrote:
> > > On 2023/6/15 0:10, Jaegeuk Kim wrote:
> > > > If there're huge # of small discards, this will increase checkpoint
> > > > latency
> > > > insanely. Let's issue small discards only by trim.
> > > >
On Tue 04-07-23 07:06:26, Bart Van Assche wrote:
> On 7/4/23 05:21, Jan Kara wrote:
> > +struct bdev_handle {
> > + struct block_device *bdev;
> > + void *holder;
> > +};
>
> Please explain in the patch description why a holder pointer is introduced
> in struct bdev_handle and how it relates t
On 7/4/23 09:14, Matthew Wilcox wrote:
On Tue, Jul 04, 2023 at 07:06:26AM -0700, Bart Van Assche wrote:
On 7/4/23 05:21, Jan Kara wrote:
+struct bdev_handle {
+ struct block_device *bdev;
+ void *holder;
+};
Please explain in the patch description why a holder pointer is introduce
On Tue 04-07-23 10:28:36, Keith Busch wrote:
> On Tue, Jul 04, 2023 at 02:21:28PM +0200, Jan Kara wrote:
> > +struct bdev_handle *blkdev_get_handle_by_dev(dev_t dev, blk_mode_t mode,
> > + void *holder, const struct blk_holder_ops *hops)
> > +{
> > + struct bdev_handle *handle = kmalloc
When evaluating in f2fs, it takes much time to obtain waf data.
This patch helps to obtain waf data without calcluation.
Signed-off-by: Beomsu Kim
---
fs/f2fs/iostat.c | 17 +
1 file changed, 17 insertions(+)
diff --git a/fs/f2fs/iostat.c b/fs/f2fs/iostat.c
index 3d5bfb1ad585..5
32 matches
Mail list logo