[f2fs-dev] [PATCH] man: update mkfs.f2fs to give the default android option

2022-03-22 Thread Jaegeuk Kim
This gives an information of "-g android". Signed-off-by: Jaegeuk Kim --- man/mkfs.f2fs.8 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/man/mkfs.f2fs.8 b/man/mkfs.f2fs.8 index 15e0bd9c25e4..a6249f6ef6ed 100644 --- a/man/mkfs.f2fs.8 +++ b/man/mkfs.f2fs.8 @@ -143,7 +143,7 @@

Re: [f2fs-dev] [GIT PULL] f2fs for 5.18

2022-03-22 Thread Linus Torvalds
On Tue, Mar 22, 2022 at 5:34 PM Tim Murray wrote: > > AFAICT, what's happening is that rwsem_down_read_slowpath > modifies sem->count to indicate that there's a pending reader while > f2fs_ckpt holds the write lock, and when f2fs_ckpt releases the write > lock, it wakes pending readers and hands t

Re: [f2fs-dev] [GIT PULL] f2fs for 5.18

2022-03-22 Thread Tim Murray via Linux-f2fs-devel
Hi Linus, On Tue, Mar 22, 2022 at 10:50 AM Linus Torvalds wrote: > > Even when people get the semantics and memory ordering right (which is > not always the case, but at least the f2fs code uses real lock > primitives - just oddly - and should thus be ok), it invariably tends > to be a sign of so

Re: [f2fs-dev] [GIT PULL] f2fs for 5.18

2022-03-22 Thread Jaegeuk Kim
Hi Linus, On 03/22, Linus Torvalds wrote: > On Tue, Mar 22, 2022 at 10:37 AM Waiman Long wrote: > > > > AFAICS, the read-unfair rwsem code is created to resolve a potential > > lock starvation problem that they found on linux-5.10.y stable tree. I > > believe I have fixed that in the v5.11 kernel

Re: [f2fs-dev] [GIT PULL] fscrypt updates for 5.18

2022-03-22 Thread pr-tracker-bot
The pull request you sent on Sun, 20 Mar 2022 21:50:19 -0700: > https://git.kernel.org/pub/scm/fs/fscrypt/fscrypt.git tags/fscrypt-for-linus has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/881b568756ae55ce7d87b9f001cbbe9d1289893e Thank you! -- Deet-doot-dot, I am a b

Re: [f2fs-dev] [GIT PULL] f2fs for 5.18

2022-03-22 Thread pr-tracker-bot
The pull request you sent on Mon, 21 Mar 2022 13:39:32 -0700: > git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git > tags/f2fs-for-5.18 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/ef510682af3dbe2f9cdae7126a1461c94e010967 Thank you! -- Deet-doot-dot,

Re: [f2fs-dev] [GIT PULL] f2fs for 5.18

2022-03-22 Thread Linus Torvalds
On Tue, Mar 22, 2022 at 10:37 AM Waiman Long wrote: > > AFAICS, the read-unfair rwsem code is created to resolve a potential > lock starvation problem that they found on linux-5.10.y stable tree. I > believe I have fixed that in the v5.11 kernel, see commit 2f06f702925 > ("locking/rwsem: Prevent p

Re: [f2fs-dev] [GIT PULL] f2fs for 5.18

2022-03-22 Thread Waiman Long
On 3/22/22 13:22, Linus Torvalds wrote: On Mon, Mar 21, 2022 at 1:39 PM Jaegeuk Kim wrote: In this cycle, f2fs has some performance improvements for Android workloads such as using read-unfair rwsems [...] I've pulled this, but that read-unfair rwsem code looks incredibly dodgy. Doing your own

Re: [f2fs-dev] [GIT PULL] f2fs for 5.18

2022-03-22 Thread Linus Torvalds
On Mon, Mar 21, 2022 at 1:39 PM Jaegeuk Kim wrote: > > In this cycle, f2fs has some performance improvements for Android workloads > such > as using read-unfair rwsems [...] I've pulled this, but that read-unfair rwsem code looks incredibly dodgy. Doing your own locking is always a bad sign, and