UFS rename: make it reliable when using SU and reaching nlink limit
ClosedPublic
Actions

Authored by kib on Jun 23 2022, 5:18 PM.

Tags

None

Referenced Files

	Unknown Object (File)
	Sat, Dec 6, 9:39 PM

	Unknown Object (File)
	Wed, Dec 3, 10:26 PM

	Unknown Object (File)
	Tue, Nov 25, 11:10 AM

	Unknown Object (File)
	Nov 17 2025, 4:56 PM

	Unknown Object (File)
	Nov 14 2025, 9:26 PM

	Unknown Object (File)
	Nov 14 2025, 9:26 PM

	Unknown Object (File)
	Nov 14 2025, 9:26 PM

	Unknown Object (File)
	Nov 14 2025, 6:42 PM

View All Files

Subscribers

imp

pho

Details

Reviewers

chs
mckusick

Commits

rGbc6d0d72f4f4: UFS rename: make it reliable when using SU and reaching nlink limit

Summary

PR: 165392
Tested by: pho

Diff Detail

Repository

rG FreeBSD src repository

Lint

Lint Not Applicable

Unit

Tests Not Applicable

Event Timeline

kib created this revision.Jun 23 2022, 5:18 PM

Herald added a subscriber: imp. · View Herald TranscriptJun 23 2022, 5:18 PM

kib requested review of this revision.Jun 23 2022, 5:18 PM

kib added a subscriber: pho.Jun 23 2022, 5:33 PM

This looks to be the correct fix.

This revision is now accepted and ready to land.Jun 24 2022, 3:44 AM

Closed by commit rGbc6d0d72f4f4: UFS rename: make it reliable when using SU and reaching nlink limit (authored by kib). · Explain WhyJun 24 2022, 2:48 PM

This revision was automatically updated to reflect the committed changes.

kib added a commit: rGbc6d0d72f4f4: UFS rename: make it reliable when using SU and reaching nlink limit.

Revision Contents
Changeset List

Path

Size

sys/

ufs/

ufs_vnops.c

95 lines

Diff 107349

View Options

UFS rename: make it reliable when using SU and reaching nlink limitClosedPublicActions