On 2020/9/4 1:48, Jaegeuk Kim wrote:
On 09/03, Daeho Jeong wrote:
From: Daeho Jeong
writepages() can be concurrently invoked for the same file by different
threads such as a thread fsyncing the file and a kworker kernel thread.
So, changing i_compr_blocks without protection is racy and we
On 09/03, Daeho Jeong wrote:
> From: Daeho Jeong
>
> writepages() can be concurrently invoked for the same file by different
> threads such as a thread fsyncing the file and a kworker kernel thread.
> So, changing i_compr_blocks without protection is racy and we need to
> protect it by changing
From: Daeho Jeong
writepages() can be concurrently invoked for the same file by different
threads such as a thread fsyncing the file and a kworker kernel thread.
So, changing i_compr_blocks without protection is racy and we need to
protect it by changing it with atomic type value. Plus, we don't
3 matches
Mail list logo
