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)
	Sun, Jan 4, 4:07 PM

	Unknown Object (File)
	Sat, Jan 3, 12:13 PM

	Unknown Object (File)
	Fri, Jan 2, 8:35 AM

	Unknown Object (File)
	Wed, Dec 24, 3:41 PM

	Unknown Object (File)
	Dec 10 2025, 10:03 PM

	Unknown Object (File)
	Dec 7 2025, 8:42 PM

	Unknown Object (File)
	Nov 26 2025, 1:27 AM

	Unknown Object (File)
	Nov 21 2025, 3:00 AM

View All 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