From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id C7EA844E052 for ; Wed, 29 Jul 2026 09:50:52 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785318654; cv=none; b=jf3WiaeJ5KiCGLkVJ8z+XfTRAErTb12zaOMehqRI3t4GLLhhf2GpxXGUhqrZOgGIuBLGseXpaZPn6rZdau6GyR8wJSM4lFM894+BLXsA+IN9LzR4/wk1PRK/9qYLpudaTfhtIFx0d/2YNL4ZlW4EGp41vx4oKCsJb3zcwp2lfk8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785318654; c=relaxed/simple; bh=5jeCVGqss6F20ZdJR9DQDzX4CgDrQEj48pigPXbSttM=; h=Message-ID:Date:MIME-Version:Cc:Subject:To:References:From: In-Reply-To:Content-Type; b=aZzp5172/b1TkAURszsJB/fvERxMLgETGfnR+zoVt85SbFcAWM95VwGVY8ymfelLCkOWs0vp4bhVZmkYuvUH0ycJkyfUH+IiowQ/7CIFNqjfD2woVqxU0tRHhPd8YXbOZFttxbZfCH0rPmuJlcCWGvwEEtT7bIhniNKOavEGWNI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=gICjKM51; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="gICjKM51" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 395C21F00A3D; Wed, 29 Jul 2026 09:50:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1785318652; bh=vDMfKUd2yk4FcfjiXUBiX+Zz6DAVLFdnG7Bp7dzarnY=; h=Date:Cc:Subject:To:References:From:In-Reply-To; b=gICjKM51UPuhxbaZIBlsLemNnbqgtyWREyuWwBnYabUJN6dndCYtQB0xPBrmS/lbQ Pr+zqKp6dgPsAQDYugJHOGB1Z9zwqn0ec5CahblyntwPQJTU/afhtG47cS46liQJms mcKsV8ac0tLXGX+gAZTuZiz8zyH68rXvnNoxb0lFKi1hy9iOwK2FSV74groEWSeHMn HIrhZOX/jgWqnT3BHIhF7B0L6OGlHPpjCcLGM47PhaoJE4xv0q2cqp/rMX2epQkFnZ B4z69nMSgN8s+pRnVNsjRCQwynTxAriEiT+M3GKtHNAAtArxBBQy4fITcJgxFPruIJ kpnO52iYRxFJA== Message-ID: <0b5f2dc2-ae67-4d3e-b5ea-9edf43b4f357@kernel.org> Date: Wed, 29 Jul 2026 17:50:49 +0800 Precedence: bulk X-Mailing-List: fstests@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Cc: chao@kernel.org Subject: Re: [PATCH v2] common/rc: support f2fs in _require_fanotify_ioerrors() To: Anand Suveer Jain , fstests@vger.kernel.org, jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net, "Darrick J. Wong" References: <20260706064326.3657995-1-chao@kernel.org> <5c11cd98-bb41-46e0-9765-e2aad57a08e4@kernel.org> <99220f8b-05d4-427f-998d-7f15a84c8805@kernel.org> Content-Language: en-US From: Chao Yu In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On 7/28/26 14:49, Zorro Lang wrote: > On Tue, Jul 28, 2026 at 10:24:10AM +0800, Chao Yu wrote: >> On 7/28/26 01:57, Zorro Lang wrote: >>> On Thu, Jul 23, 2026 at 05:09:12PM +0800, Chao Yu wrote: >>>> On 7/17/26 18:47, Zorro Lang wrote: >>>>> On Wed, Jul 08, 2026 at 11:25:37AM +0800, Chao Yu wrote: >>>>>> On 7/7/26 18:13, Anand Suveer Jain wrote: >>>>>>> On 6/7/26 14:43, Chao Yu wrote: >>>>>>>> f2fs has supported to report fserror, this patch adds support for f2fs >>>>>>>> in _require_fanotify_ioerrors(), so that we can run generic/791 on f2fs. >>>>>>>> >>>>>>>> Cc: Darrick J. Wong >>>>>>>> Signed-off-by: Chao Yu >>>>>>>> --- >>>>>>>> common/rc | 3 +++ >>>>>>>> 1 file changed, 3 insertions(+) >>>>>>>> >>>>>>>> diff --git a/common/rc b/common/rc >>>>>>>> index 494725547..f51ad59f3 100644 >>>>>>>> --- a/common/rc >>>>>>>> +++ b/common/rc >>>>>>>> @@ -6257,6 +6257,9 @@ _require_fanotify_ioerrors() >>>>>>>> x="$(_get_fs_sysfs_attr $TEST_DEV err_report_sec)" >>>>>>>> test -n "$x" && return 0 >>>>>>>> ;; >>>>>>> >>>>>>> >>>>>>>> + f2fs) >>>>>>>> + x="$(cat /sys/fs/f2fs/features/fserror)" >>>>>>>> + test -n "$x" && return 0 >>>>>>> >>>>>>> Don't we need to check if /sys/fs/f2fs/features/fserror >>>>>>> is present in the running kernel (there are helpers) >>>>>> >>>>>> Hi Anand, >>>>>> >>>>>> You mean _has_fs_sysfs_attr()? however, it forces to check first parameter $dev >>>>>> w/ block device type: >>>>>> >>>>>> if [ ! -b "$dev" -o -z "$attr" ];then >>>>>> _fail "Usage: _has_fs_sysfs_attr " >>>>>> fi >>>>> >>>>> Hi Chao and Anand, >>>>> >>>>> The *_fs_sysfs related helpers were brought in by me in: >>>>> commit 2a7b77abcd1dde735186b363da24540706c43b73 >>>>> Author: Zorro Lang >>>>> Date: Tue Jul 5 17:30:24 2016 +0800 >>>>> >>>>> xfs: configurable behavior on errors at unmount time >>>>> >>>>> At that time, I didn't think about the "features/" directory. >>>>> >>>>> Now, let me rethink this set of helpers. I feel that the *_fs_sysfs >>>>> family of functions shouldn't be restricted to the $dev directory, >>>>> we should remove this restriction. >>>>> >>>>> Following that, we bring in *_fs_sysfs_device (appending the _device suffix) >>>>> helpers which call *_fs_sysfs(). Also change the test cases who call these >>>>> functions. >>>>> >>>>> Finally, we can introduce the *_fs_sysfs_features functions (or simply use >>>>> *_fs_sysfs directly). >>>>> >>>>> Also, we have both *_fs_sysfs_attr and *_fs_sysfs, and the logic between >>>>> them is somewhat confusing and easy to mix up. >>>> >>>> Zorro, >>>> >>>> It makes sense, and good news to their user. Thanks for the proposal. >>>> >>>>> >>>>> I need to write a series of patches to clean up these logic. For this current >>>>> patch, we can start with a small-scale change first. What do you think? >>>> >>>> So I will use this first: >>>> >>>> f2fs) >>>> local feat_file="/sys/fs/f2fs/features/fserror" >>>> if [ -f "$feat_file" ] && [ "$(cat "$feat_file")" = "supported" ]; then >>>> return 0 >>>> fi >>>> ;; >>>> >>>> And then waiting for your cleanup? or if you want to clean up this, please do it >>>> directly while merging. >>> >>> If f2fs wants to test this feature right away, I can merge your patch now and >>> clean it up later. If it's not urgent, I'll take care of it all together. >> >> Zorro, >> >> Could you please help to merge it first? so that we can test 791 w/ last >> upstream code, and also in case we missed to track its status to lose it. :P > > Sure, I'm good to have this first. Could you send a new patch version, if you'd > like to change it? Have sent v3, please take a look. :) Thanks, > > Thanks, > Zorro > >> >> Thanks, >> >>> >>> Thanks, >>> Zorro >>> >>>> >>>> Thanks, >>>> >>>>> >>>>> Thanks, >>>>> Zorro >>>>> >>>>>> >>>>>> >>>>>>> before reading it? >>>>>> >>>>>> How about this? >>>>>> >>>>>> f2fs) >>>>>> local feat_file="/sys/fs/f2fs/features/fserror" >>>>>> if [ -f "$feat_file" ] && [ "$(cat "$feat_file")" = "supported" ]; then >>>>>> return 0 >>>>>> fi >>>>>> ;; >>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>>> esac >>>>>>>> _notrun "$FSTYP does not support fanotify ioerrors" >>>>>>> >>>>>> >>>> >>>> >> From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.sourceforge.net (lists.sourceforge.net [216.105.38.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id E5DDEC53200 for ; Wed, 29 Jul 2026 09:51:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.sourceforge.net; s=beta; h=Content-Transfer-Encoding:Content-Type: Reply-To:From:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:Subject:In-Reply-To:References:To:MIME-Version:Date: Message-ID:Sender:Cc:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=i4eWUkfA2ZgDJicpw0qO20iUYENi1kHj4tNbYhBcGnA=; b=f4fEMDmUdaqFwImPyGZ1vUb33Q ZAu7BWP88EsZDt8Qq0a5y0ttWV58kxhfjdvHzLQJ9EiKRTu+CbLBL0LlSw/gNkyAdH0U9wL8h8kP/ KReQWy+Fa8E2eMoyh0lv7BbBcTB2FUUBsdyvTIWWAMZ/ts9OEDNo9S9S+d7NuThwFkhY=; Received: from [127.0.0.1] (helo=sfs-ml-2.v29.lw.sourceforge.com) by sfs-ml-2.v29.lw.sourceforge.com with esmtp (Exim 4.95) (envelope-from ) id 1wp0wX-0007Gw-Qh; Wed, 29 Jul 2026 09:51:18 +0000 Received: from [172.30.29.66] (helo=mx.sourceforge.net) by sfs-ml-2.v29.lw.sourceforge.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from ) id 1wp0wE-0007GX-LA for linux-f2fs-devel@lists.sourceforge.net; Wed, 29 Jul 2026 09:50:59 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sourceforge.net; s=x; h=Content-Transfer-Encoding:Content-Type:In-Reply-To: From:References:To:Subject:Cc:MIME-Version:Date:Message-ID:Sender:Reply-To: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=vDMfKUd2yk4FcfjiXUBiX+Zz6DAVLFdnG7Bp7dzarnY=; b=bENj04tGjckicNLVzECtFyFVUn wjpHjCbtPSDGLTCAM8mbANYxeshif/mlbkPibzDCXVo/Lf6UE+pOVhk7yTZkdsnJGIoTJowEra7Ll B6Wu30Gn/LKqZqOsJdFcsVMTPgfXXberrC89J9dEacRJt/Fn1sya5vjPqNYJ2UQ7VXUE=; DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sf.net; s=x ; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:From:References:To: Subject:Cc:MIME-Version:Date:Message-ID:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=vDMfKUd2yk4FcfjiXUBiX+Zz6DAVLFdnG7Bp7dzarnY=; b=ePbHlBnol306SArFe8KsWyyg5U hBht6UUHes74B1hX67WUHfogc19Lppc4VHFRl3URwElShSQqV+Q8iHkw1TshUL6Xm380OVYGTRDBd yiYYcqbOqoXySCowC3GcIFjnLufabkUC7FjjTOVnlxBXwhx0VWkx199wNOWMTOlMvU+8=; Received: from sea.source.kernel.org ([172.234.252.31]) by sfi-mx-1.v28.lw.sourceforge.com with esmtps (TLS1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.95) id 1wp0wH-0001lI-Ij for linux-f2fs-devel@lists.sourceforge.net; Wed, 29 Jul 2026 09:50:59 +0000 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) by sea.source.kernel.org (Postfix) with ESMTP id 83C0C41223 for ; Wed, 29 Jul 2026 09:50:52 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 395C21F00A3D; Wed, 29 Jul 2026 09:50:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1785318652; bh=vDMfKUd2yk4FcfjiXUBiX+Zz6DAVLFdnG7Bp7dzarnY=; h=Date:Cc:Subject:To:References:From:In-Reply-To; b=gICjKM51UPuhxbaZIBlsLemNnbqgtyWREyuWwBnYabUJN6dndCYtQB0xPBrmS/lbQ Pr+zqKp6dgPsAQDYugJHOGB1Z9zwqn0ec5CahblyntwPQJTU/afhtG47cS46liQJms mcKsV8ac0tLXGX+gAZTuZiz8zyH68rXvnNoxb0lFKi1hy9iOwK2FSV74groEWSeHMn HIrhZOX/jgWqnT3BHIhF7B0L6OGlHPpjCcLGM47PhaoJE4xv0q2cqp/rMX2epQkFnZ B4z69nMSgN8s+pRnVNsjRCQwynTxAriEiT+M3GKtHNAAtArxBBQy4fITcJgxFPruIJ kpnO52iYRxFJA== Message-ID: <0b5f2dc2-ae67-4d3e-b5ea-9edf43b4f357@kernel.org> Date: Wed, 29 Jul 2026 17:50:49 +0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: Anand Suveer Jain , fstests@vger.kernel.org, jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net, "Darrick J. Wong" References: <20260706064326.3657995-1-chao@kernel.org> <5c11cd98-bb41-46e0-9765-e2aad57a08e4@kernel.org> <99220f8b-05d4-427f-998d-7f15a84c8805@kernel.org> Content-Language: en-US In-Reply-To: X-Headers-End: 1wp0wH-0001lI-Ij Subject: Re: [f2fs-dev] [PATCH v2] common/rc: support f2fs in _require_fanotify_ioerrors() X-BeenThere: linux-f2fs-devel@lists.sourceforge.net X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Chao Yu via Linux-f2fs-devel Reply-To: Chao Yu Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-f2fs-devel-bounces@lists.sourceforge.net On 7/28/26 14:49, Zorro Lang wrote: > On Tue, Jul 28, 2026 at 10:24:10AM +0800, Chao Yu wrote: >> On 7/28/26 01:57, Zorro Lang wrote: >>> On Thu, Jul 23, 2026 at 05:09:12PM +0800, Chao Yu wrote: >>>> On 7/17/26 18:47, Zorro Lang wrote: >>>>> On Wed, Jul 08, 2026 at 11:25:37AM +0800, Chao Yu wrote: >>>>>> On 7/7/26 18:13, Anand Suveer Jain wrote: >>>>>>> On 6/7/26 14:43, Chao Yu wrote: >>>>>>>> f2fs has supported to report fserror, this patch adds support for f2fs >>>>>>>> in _require_fanotify_ioerrors(), so that we can run generic/791 on f2fs. >>>>>>>> >>>>>>>> Cc: Darrick J. Wong >>>>>>>> Signed-off-by: Chao Yu >>>>>>>> --- >>>>>>>> common/rc | 3 +++ >>>>>>>> 1 file changed, 3 insertions(+) >>>>>>>> >>>>>>>> diff --git a/common/rc b/common/rc >>>>>>>> index 494725547..f51ad59f3 100644 >>>>>>>> --- a/common/rc >>>>>>>> +++ b/common/rc >>>>>>>> @@ -6257,6 +6257,9 @@ _require_fanotify_ioerrors() >>>>>>>> x="$(_get_fs_sysfs_attr $TEST_DEV err_report_sec)" >>>>>>>> test -n "$x" && return 0 >>>>>>>> ;; >>>>>>> >>>>>>> >>>>>>>> + f2fs) >>>>>>>> + x="$(cat /sys/fs/f2fs/features/fserror)" >>>>>>>> + test -n "$x" && return 0 >>>>>>> >>>>>>> Don't we need to check if /sys/fs/f2fs/features/fserror >>>>>>> is present in the running kernel (there are helpers) >>>>>> >>>>>> Hi Anand, >>>>>> >>>>>> You mean _has_fs_sysfs_attr()? however, it forces to check first parameter $dev >>>>>> w/ block device type: >>>>>> >>>>>> if [ ! -b "$dev" -o -z "$attr" ];then >>>>>> _fail "Usage: _has_fs_sysfs_attr " >>>>>> fi >>>>> >>>>> Hi Chao and Anand, >>>>> >>>>> The *_fs_sysfs related helpers were brought in by me in: >>>>> commit 2a7b77abcd1dde735186b363da24540706c43b73 >>>>> Author: Zorro Lang >>>>> Date: Tue Jul 5 17:30:24 2016 +0800 >>>>> >>>>> xfs: configurable behavior on errors at unmount time >>>>> >>>>> At that time, I didn't think about the "features/" directory. >>>>> >>>>> Now, let me rethink this set of helpers. I feel that the *_fs_sysfs >>>>> family of functions shouldn't be restricted to the $dev directory, >>>>> we should remove this restriction. >>>>> >>>>> Following that, we bring in *_fs_sysfs_device (appending the _device suffix) >>>>> helpers which call *_fs_sysfs(). Also change the test cases who call these >>>>> functions. >>>>> >>>>> Finally, we can introduce the *_fs_sysfs_features functions (or simply use >>>>> *_fs_sysfs directly). >>>>> >>>>> Also, we have both *_fs_sysfs_attr and *_fs_sysfs, and the logic between >>>>> them is somewhat confusing and easy to mix up. >>>> >>>> Zorro, >>>> >>>> It makes sense, and good news to their user. Thanks for the proposal. >>>> >>>>> >>>>> I need to write a series of patches to clean up these logic. For this current >>>>> patch, we can start with a small-scale change first. What do you think? >>>> >>>> So I will use this first: >>>> >>>> f2fs) >>>> local feat_file="/sys/fs/f2fs/features/fserror" >>>> if [ -f "$feat_file" ] && [ "$(cat "$feat_file")" = "supported" ]; then >>>> return 0 >>>> fi >>>> ;; >>>> >>>> And then waiting for your cleanup? or if you want to clean up this, please do it >>>> directly while merging. >>> >>> If f2fs wants to test this feature right away, I can merge your patch now and >>> clean it up later. If it's not urgent, I'll take care of it all together. >> >> Zorro, >> >> Could you please help to merge it first? so that we can test 791 w/ last >> upstream code, and also in case we missed to track its status to lose it. :P > > Sure, I'm good to have this first. Could you send a new patch version, if you'd > like to change it? Have sent v3, please take a look. :) Thanks, > > Thanks, > Zorro > >> >> Thanks, >> >>> >>> Thanks, >>> Zorro >>> >>>> >>>> Thanks, >>>> >>>>> >>>>> Thanks, >>>>> Zorro >>>>> >>>>>> >>>>>> >>>>>>> before reading it? >>>>>> >>>>>> How about this? >>>>>> >>>>>> f2fs) >>>>>> local feat_file="/sys/fs/f2fs/features/fserror" >>>>>> if [ -f "$feat_file" ] && [ "$(cat "$feat_file")" = "supported" ]; then >>>>>> return 0 >>>>>> fi >>>>>> ;; >>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>>> esac >>>>>>>> _notrun "$FSTYP does not support fanotify ioerrors" >>>>>>> >>>>>> >>>> >>>> >> _______________________________________________ Linux-f2fs-devel mailing list Linux-f2fs-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel