Re: [PATCH 1/1] f2fs: release locks before return in f2fs_ioc_gc_range()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: sunqiuyang <sunqiuyang@xxxxxxxxxx>, <linux-kernel@xxxxxxxxxxxxxxx>, <linux-fsdevel@xxxxxxxxxxxxxxx>, <linux-f2fs-devel@xxxxxxxxxxxxxxxxxxxxx>
Subject: Re: [PATCH 1/1] f2fs: release locks before return in f2fs_ioc_gc_range()
From: Chao Yu <yuchao0@xxxxxxxxxx>
Date: Fri, 16 Mar 2018 16:21:23 +0800
In-reply-to: <20180313114250.29211-1-sunqiuyang@huawei.com>
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0

On 2018/3/13 19:42, sunqiuyang wrote:
> From: Qiuyang Sun <sunqiuyang@xxxxxxxxxx>
> 
> Currently, we will leave the kernel with locks still held when the gc_range
> is invalid. This patch fixes the bug.
> 
> Signed-off-by: Qiuyang Sun <sunqiuyang@xxxxxxxxxx>

Reviewed-by: Chao Yu <yuchao0@xxxxxxxxxx>

Thanks,

References:
- [PATCH 1/1] f2fs: release locks before return in f2fs_ioc_gc_range()
  - From: sunqiuyang

Prev by Date: [PATCH] fs: don't flush pagecache when expanding block device
Next by Date: [RFC PATCH ghak32 V2 04/13] audit: add containerid filtering
Previous by thread: [PATCH 1/1] f2fs: release locks before return in f2fs_ioc_gc_range()
Next by thread: [PATCH] dcache: fix indirectly reclaimable memory accounting
Index(es):
- Date
- Thread

[Index of Archives] [Linux Ext4 Filesystem] [Union Filesystem] [Filesystem Testing] [Ceph Users] [Ecryptfs] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [Samba] [Device Mapper] [CEPH Development]

Powered by Linux