Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp2695430pxb; Fri, 5 Nov 2021 03:10:56 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy4c0It8Zd+hxg6GS48hCPaPxxki5MXwASYd8D2XngDk98nu+FJJNzroNG517PkNlnfLvQE X-Received: by 2002:a50:da48:: with SMTP id a8mr76848102edk.155.1636107056573; Fri, 05 Nov 2021 03:10:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1636107056; cv=none; d=google.com; s=arc-20160816; b=yIRwuVC0W9nhYls+hVi4DzKlJxNJgd7N+KR8HvHf0ca1S7B+mQbHm1F7NtndQxzJlt 5BF/xjp8CyghopLpsoV3EwPH3AVw4KKdY2oOippN4B//leZVkVf6i9a4ZOo2TAjF/QRN TAT9Jf92GCIOCT1LzkN8P4SYbJJbnmu5DoOVJ7FboY/AcWtNiJ16qJWLG9JO9psmQ8Qg lWKEIHCsNrJG0sYtymHERroyf1P5OtPN5Vv7N3F4AgOawZ2bAfR7fhRYwmeUrSwcsWxy 6PpWnxjURz5Kls6mD6I/jj9/WWsS/Yl5EGe7rtSZHadSYvXNEkyWXMu3XV2EvjR2qi+7 bMqQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:reply-to:message-id:subject:cc:to:from:date :dkim-signature:dkim-signature; bh=5Wqby23pgih4bJELPymWZZdR5S0E6N3dTsc6SakmTbY=; b=qyqZ2oN1nUnXsG/Z5wUt5Zfbb017un2gGh/ZSrUtJlG5jHpHcTKTEHnix85NtiJEkc svNE+E5JFIgHTxZ5iqILjzgrNRaLYvWI4ifF6n7VpIrK8aN1bucps0OkxTI8tLLRBSOa t9cwPZwIuAfe2w8EIoH6ImwB8BQ4f/9lzgur5Fya5FYN5bDUt3JiWnsvXZb6nmVXo3zB eItOcwk1pPWVSdhMGz6pDjOCME0E9wZOOMfdxhaYA1hfejjhpEv2SoutM+uXJa+2G3kw UsNce2Z0+gF5NTU7cCTSdayR7N1DXKd9vrWGwUGlAjfgCo43/wgxswCfHZht8r5NJICL JfVA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@suse.cz header.s=susede2_rsa header.b=Qt6VwAEC; dkim=neutral (no key) header.i=@suse.cz header.s=susede2_ed25519; spf=pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id w4si14153385edd.413.2021.11.05.03.10.26; Fri, 05 Nov 2021 03:10:56 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@suse.cz header.s=susede2_rsa header.b=Qt6VwAEC; dkim=neutral (no key) header.i=@suse.cz header.s=susede2_ed25519; spf=pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232883AbhKEKNE (ORCPT + 99 others); Fri, 5 Nov 2021 06:13:04 -0400 Received: from smtp-out1.suse.de ([195.135.220.28]:52598 "EHLO smtp-out1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230110AbhKEKND (ORCPT ); Fri, 5 Nov 2021 06:13:03 -0400 Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id 9E9BB212C0; Fri, 5 Nov 2021 10:10:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_rsa; t=1636107023; h=from:from:reply-to:reply-to:date:date:message-id:message-id:to:to: cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=5Wqby23pgih4bJELPymWZZdR5S0E6N3dTsc6SakmTbY=; b=Qt6VwAECDU5YCDHsziGa5nLocz3jpcEgbcgdHexeAE+xvpdcamQni+28BfF68+so6byldz qZBHZoUF5b2p8+pulV2Tn8FHPf9vW0HX6OeFd+oGNjiV8vpAVFntac91DM4FP5ILKi1Z/T jwyR/26i6PsdqQFhF/GEY7xGfv8WKp0= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_ed25519; t=1636107023; h=from:from:reply-to:reply-to:date:date:message-id:message-id:to:to: cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=5Wqby23pgih4bJELPymWZZdR5S0E6N3dTsc6SakmTbY=; b=D2+jMNhnlhfNiG4WVuADOBiJoHNf2AvRtA1hSYPKiZSbONd4Qis0FKJXgSJ57luXq035iI 6mIqWHgAtgtGb0DA== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 3C54E13B97; Fri, 5 Nov 2021 10:10:23 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id 6dOmDA8DhWGjewAAMHmgww (envelope-from ); Fri, 05 Nov 2021 10:10:23 +0000 Date: Fri, 5 Nov 2021 11:10:21 +0100 From: Petr Vorel To: Gabriel Krisman Bertazi Cc: jack@suse.com, amir73il@gmail.com, repnop@google.com, linux-ext4@vger.kernel.org, kernel@collabora.com, khazhy@google.com, ltp@lists.linux.it Subject: Re: [LTP] [PATCH v3 0/9] Test the new fanotify FAN_FS_ERROR event Message-ID: Reply-To: Petr Vorel References: <20211029211732.386127-1-krisman@collabora.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20211029211732.386127-1-krisman@collabora.com> Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org Hi Gabriel, all, > Hi, > Now that FAN_FS_ERROR is close to being merged, I'm sending a new > version of the LTP tests. This is the v3 of this patchset, and it > applies the feedback of the previous version, in particular, it solves > the issue Amir pointed out, that ltp won't gracefully handle a test with > tcnt==0. To solve that, I merged the patch that set up the environment > with a simple test, that only triggers a fs abort and watches the > event. > I'm also renaming the testcase from fanotify20 to fanotify21, to leave > room for the pidfs test that is also in the baking by Matthew Bobrowski. > One important detail is that, for the tests to succeed, there is a > dependency on an ext4 fix I sent a few days ago: > https://lore.kernel.org/linux-ext4/20211026173302.84000-1-krisman@collabora.com/T/#u It has been merged into Theodore Ts'o ext4 tree into dev branch as c1e2e0350ce3 ("ext4: Fix error code saved on super block during file system abort") We should probably add it as .tags (see fanotify06.c). Also it'd be nice just to mention relevant commits which added FAN_FS_ERROR in fanotify21.c (probably "fanotify: Allow users to request FAN_FS_ERROR events" ?) + kernel version it added it -suppose 5.16 (although it can be backported; and these commits should not go to .tags, as we track there only fixes not new features). I can add it myself (no need to repost). Kind regards, Petr