fusefs: Initialize a pad word in the mknod message
ClosedPublic
Actions

Authored by markj on Mar 17 2022, 10:14 PM.

Tags

None

Referenced Files

	Unknown Object (File)
	Feb 8 2025, 5:48 AM

	Unknown Object (File)
	Feb 5 2025, 6:30 PM

	Unknown Object (File)
	Jan 30 2025, 7:53 AM

	Unknown Object (File)
	Jan 29 2025, 6:22 AM

	Unknown Object (File)
	Jan 29 2025, 1:33 AM

	Unknown Object (File)
	Jan 28 2025, 3:16 AM

	Unknown Object (File)
	Jan 27 2025, 4:56 PM

	Unknown Object (File)
	Jan 24 2025, 5:54 PM

View All 55 Files

Subscribers

imp

Details

Reviewers

asomers

Commits

rGc0b98fe16f25: fusefs: Initialize a pad word in the mknod message

Summary

Reported by: Jenkins (KMSAN job)
MFC after: 3 days

Diff Detail

Repository

rG FreeBSD src repository

Lint

Lint Not Applicable

Unit

Tests Not Applicable

Event Timeline

markj created this revision.Mar 17 2022, 10:14 PM

Herald added a subscriber: imp. · View Herald TranscriptMar 17 2022, 10:14 PM

markj requested review of this revision.Mar 17 2022, 10:14 PM

Harbormaster completed remote builds in B44814: Diff 103963.Mar 17 2022, 10:14 PM

LGTM

This revision is now accepted and ready to land.Mar 17 2022, 10:23 PM

Closed by commit rGc0b98fe16f25: fusefs: Initialize a pad word in the mknod message (authored by markj). · Explain WhyMar 17 2022, 10:31 PM

This revision was automatically updated to reflect the committed changes.

markj added a commit: rGc0b98fe16f25: fusefs: Initialize a pad word in the mknod message.

Revision Contents
Changeset List

Path

Size

sys/

fs/

fuse/

fuse_internal.c

1 line

Diff 103964

View Options

sys/fs/fuse/fuse_internal.c

fusefs: Initialize a pad word in the mknod messageClosedPublicActions