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 X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1DEF6C43331 for ; Wed, 25 Mar 2020 11:20:15 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id EA25F20771 for ; Wed, 25 Mar 2020 11:20:14 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="tmunX6WR" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727137AbgCYLUO (ORCPT ); Wed, 25 Mar 2020 07:20:14 -0400 Received: from mail-il1-f195.google.com ([209.85.166.195]:42052 "EHLO mail-il1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727046AbgCYLUO (ORCPT ); Wed, 25 Mar 2020 07:20:14 -0400 Received: by mail-il1-f195.google.com with SMTP id f16so1446293ilj.9 for ; Wed, 25 Mar 2020 04:20:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=rR4xNt2k6k2Y4W/2DM6BrcOKVsemPNYbjCMjGKwzivs=; b=tmunX6WRa/ZsWAgH+2rSKmdMIlzD6UES7xgWs3A4Q12lBr8KfXxrBWPIwMMsPlEnT6 W5fJTrCMHgBmdjdJ9gVyiP4L9wasPMM8VLOXZaW0ABe+GU7iCBdr3S+84At/5jvRXNe0 qjDyC5zaLk+1HaBQbYFD/mUmOwODloEQmG1xcdfBv691DCOgRDydG+pdLqTERidXvyDY Z/XlTNucW9VxUm1w6VmcDzBesitkNes8bOFoJeJeJeoRhp4AK3AIhi/gXRlBsA2JBaCd +kPAJGTcHlCK4fl5XWikE7aokzkJ4dIBp0QPQ6dR48GlmgbQp/JhtVT9MawWytBMm3oN +GFQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=rR4xNt2k6k2Y4W/2DM6BrcOKVsemPNYbjCMjGKwzivs=; b=QM0X8RJ15ukXoxVYfCXRBsf1JOGZRvm0uDKdJ9xWzs96tHsF8JQCP6wUoEy7rhJCMP P+8N6O6wtriCOf/zpreYCC8JIylvq7l/HB/7lPSeF+n6R2hXZSm9CgSOXEH1DEQGb8O+ 0RJLlgvChitBFsllPx3rAa8XVb9SjFjSetDrBNaC8AYgmwbqCytH5YVHvZMc7kanPR3q yQs5bynNQw+ode0Do4C2mBBotbfFA3ZrRlIx7dEocFiyMAxNkFfEkocxF33FExGeHXae Fah/Hj+lbiI3iRrV7c5u4iZ/Qtpxa9cXoWrKZW8kS7GJB3TN7Fj6iWp3nExFyFLXZ3tn Nn4w== X-Gm-Message-State: ANhLgQ06t4uI3ie2A9nPp9gORub+4upvNm2hh5bNMuPmWNJkkwNDBbB6 m+xV+IsdsKWOVFT+PixtpS25BYxS6tE1BTzcvPw= X-Google-Smtp-Source: ADFU+vscNFSZEziZHyLbUkl6kaoTpobcSoE0/mDIYB67trUXE0oVRxO6UCIc3G2jEEx93IRHXwKnJXQJqKvyoEEbD7Q= X-Received: by 2002:a05:6e02:68a:: with SMTP id o10mr1850939ils.72.1585135213385; Wed, 25 Mar 2020 04:20:13 -0700 (PDT) MIME-Version: 1.0 References: <20200319151022.31456-1-amir73il@gmail.com> <20200319151022.31456-7-amir73il@gmail.com> <20200325102257.GH28951@quack2.suse.cz> In-Reply-To: <20200325102257.GH28951@quack2.suse.cz> From: Amir Goldstein Date: Wed, 25 Mar 2020 13:20:02 +0200 Message-ID: Subject: Re: [PATCH v3 06/14] fsnotify: pass dentry instead of inode for events possible on child To: Jan Kara Cc: Al Viro , linux-fsdevel Content-Type: text/plain; charset="UTF-8" Sender: linux-fsdevel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org On Wed, Mar 25, 2020 at 12:22 PM Jan Kara wrote: > > On Thu 19-03-20 17:10:14, Amir Goldstein wrote: > > Most events that can be reported to watching parent pass > > FSNOTIFY_EVENT_PATH as event data, except for FS_ARRTIB and FS_MODIFY > > as a result of truncate. > > > > Define a new data type to pass for event - FSNOTIFY_EVENT_DENTRY > > and use it to pass the dentry instead of it's ->d_inode for those events. > > > > Soon, we are going to use the dentry data type to report events > > with name info in fanotify backend. > > > > Signed-off-by: Amir Goldstein > > I've skipped this patch because FSNOTIFY_EVENT_DENTRY is not used by > anything in this series... Just that you don't wonder when rebasing later. > No problem. I had my series ordered fsnotify then fanotify, that's why it was there. It really belongs to the FAN_REPORT_NAME patches. Thanks, Amir.