Skip to contentSkip to conversation

New: fanotify reports parent PPID insted of PID for FAN_MODIFY events

Bug 216775 [email protected] 2 participants 5 messages Dec 5, 2022

lore
Share & tools
lore
#0 lore 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: [email protected]
          Reporter: [email protected]
        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 [email protected]:opcoder0/fanotify.git
cd fanotify
sudo go test -v

The test "TestWithCapSysAdmFanotifyFileModified" fails reporting pid mismatch.

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.
#1 lore raw
Quoted 33 lines · On Mon, Dec 5, 2022 at 7:02 AM <[email protected]> wrote:

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: [email protected]
          Reporter: [email protected]
        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

Quoted 8 lines

It can be reproduced by -

git clone [email protected]:opcoder0/fanotify.git
cd fanotify
sudo go test -v

The test "TestWithCapSysAdmFanotifyFileModified" fails reporting pid mismatch.

It's a test bug.
The modify event with self pid is generated by os.WriteFile() Either change test to expect modify event with self pid or move test file creation before starting the listener.

Thanks,
Amir.

#2 lore raw

[Bug 216775] fanotify reports parent PPID insted of PID for FAN_MODIFY events

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=216775

--- Comment #1 from Amir Goldstein ([email protected]) ---

Quoted 36 lines · On Mon, Dec 5, 2022 at 7:02 AM <[email protected]> wrote:

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: [email protected]
          Reporter: [email protected]
        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

Quoted 9 lines

It can be reproduced by -

git clone [email protected]:opcoder0/fanotify.git
cd fanotify
sudo go test -v

The test "TestWithCapSysAdmFanotifyFileModified" fails reporting pid mismatch.

It's a test bug.
The modify event with self pid is generated by os.WriteFile() Either change test to expect modify event with self pid or move test file creation before starting the listener.

Thanks,
Amir.

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.
#4 lore raw

[Bug 216775] fanotify reports parent PPID insted of PID for FAN_MODIFY events

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=216775

opcoder0 ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #3 from opcoder0 ([email protected]) --- Test issue.

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.