From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 216775] New: fanotify reports parent PPID insted of PID for FAN_MODIFY events
Date: Mon, 05 Dec 2022 04:38:02 +0000 [thread overview]
Message-ID: <bug-216775-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=216775
Bug ID: 216775
Summary: fanotify reports parent PPID insted of PID for
FAN_MODIFY events
Product: File System
Version: 2.5
Kernel Version: 5.15.0
Hardware: Intel
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: ext4
Assignee: fs_ext4@kernel-bugs.osdl.org
Reporter: saikiran.gummaraj@icloud.com
Regression: No
Hello,
While I've been developing a library around fanotify in Go, I noticed that
fanotify subsystem reports the parent process ID in fanotify_event_metadata.pid
instead of the Process ID when mask is set to FAN_MODIFY. I was able to confirm
the error through a test and also manually verifying the PIDs in the audit log.
I did not observe this behaviour for FAN_ACCESS bit.
I've been able to reproduce this on -
Ubuntu 20.04.5 - 5.15.0-53-generic
Ubuntu 22.10 - 5.19.0-23-generic
It can be reproduced by -
git clone git@github.com:opcoder0/fanotify.git
cd fanotify
sudo go test -v
The test "TestWithCapSysAdmFanotifyFileModified" fails reporting pid mismatch.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2022-12-05 4:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 4:38 bugzilla-daemon [this message]
2022-12-05 8:44 ` [Bug 216775] New: fanotify reports parent PPID insted of PID for FAN_MODIFY events Amir Goldstein
2022-12-05 8:45 ` [Bug 216775] " bugzilla-daemon
2022-12-05 9:18 ` bugzilla-daemon
2022-12-05 9:19 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-216775-13602@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.