Add advisory file locking support to fuse.
Needs ReviewPublic
Actions

Authored by rmacklem on Dec 21 2015, 11:32 PM.

Tags

None

Referenced Files

	Unknown Object (File)
	Wed, Jan 29, 12:01 AM

	Unknown Object (File)
	Sat, Jan 11, 11:58 AM

	Unknown Object (File)
	Nov 15 2024, 6:58 AM

	Unknown Object (File)
	Nov 11 2024, 4:08 PM

	Unknown Object (File)
	Nov 7 2024, 7:55 PM

	Unknown Object (File)
	Oct 31 2024, 6:18 AM

	Unknown Object (File)
	Oct 29 2024, 6:32 PM

	Unknown Object (File)
	Oct 27 2024, 7:56 AM

View All 60 Files

Subscribers

imp

This revision needs review, but there are no reviewers specified.

Details

Reviewers: None

Summary

This patch adds advisory byte range locking support to fuse.

Test Plan

This patch has been tested minimally with GlusterFS.

Diff Detail

Repository

rS FreeBSD src repository - subversion

Lint

Lint Skipped

Unit

Tests Skipped

Event Timeline

rmacklem updated this revision to Diff 11540.Dec 21 2015, 11:32 PM

rmacklem retitled this revision from to Add advisory file locking support to fuse..

rmacklem updated this object.

rmacklem edited the test plan for this revision. (Show Details)

rmacklem set the repository for this revision to rS FreeBSD src repository - subversion.

Herald added a subscriber: imp. · View Herald TranscriptDec 21 2015, 11:32 PM

This is the second in a series of patches for fuse that I needed to
implement so that I can use GlusterFS as part of a pNFS server cluster.
I don't know if there are other fuse file systems that support byte range locking?

Revision Contents
Changeset List

Path

Size

fs/

fuse/

	fuse_ipc.c
	fuse_ipc.c.sav2

6 lines

	fuse_vnops.c
	fuse_vnops.c.sav2

170 lines

Diff 11540

View Options

fs/fuse/fuse_ipc.c