From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-f66.google.com ([209.85.221.66]:34287 "EHLO mail-wr1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2390180AbeIVAKo (ORCPT ); Fri, 21 Sep 2018 20:10:44 -0400 Received: by mail-wr1-f66.google.com with SMTP id t15so5818219wrx.1 for ; Fri, 21 Sep 2018 11:20:39 -0700 (PDT) From: Amir Goldstein To: Jan Kara Cc: nixiaoming@huawei.com, linux-fsdevel@vger.kernel.org Subject: [PATCH v2 0/2] New fanotify event info API Date: Fri, 21 Sep 2018 21:20:29 +0300 Message-Id: <20180921182031.3184-1-amir73il@gmail.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Jan, Reposting my slightly modified cleanup patch along with the patch from nixiaoming that uses it to add a new fanotify_init() flag. After a few review cycles with nixiaoming, per his request, I took his FAN_EVENT_INFO_TID patch to my tree, fixes a couple of issues including commit message wording and tested it. For me, the new API seems very intuitive, not sure why thread id was not reported to begin with, but if you like more concrete use cases, you will need to ask them from nixiaoming. Thanks, Amir. Amir Goldstein (1): fanotify: store fanotify_init() flags in group's fanotify_data nixiaoming (1): fanotify: support reporting thread id instead of process id fs/notify/fanotify/fanotify.c | 9 ++++++--- fs/notify/fanotify/fanotify.h | 2 +- fs/notify/fanotify/fanotify_user.c | 10 +++++----- fs/notify/fdinfo.c | 24 +----------------------- include/linux/fanotify.h | 4 ++++ include/linux/fsnotify_backend.h | 4 ++-- include/uapi/linux/fanotify.h | 9 +++++++-- 7 files changed, 26 insertions(+), 36 deletions(-) -- 2.17.1