Page MenuHomeFreeBSD

net/samba419: Fix procfd search patterns for FreeBSD
ClosedPublic

Authored by michaelo on Fri, Jan 3, 8:21 PM.
Tags
None
Referenced Files
F107344728: D48313.diff
Sun, Jan 12, 7:21 PM
F107290829: D48313.diff
Sun, Jan 12, 1:55 AM
Unknown Object (File)
Sat, Jan 11, 3:35 AM
Unknown Object (File)
Fri, Jan 10, 12:44 AM
Unknown Object (File)
Fri, Jan 10, 12:12 AM
Unknown Object (File)
Wed, Jan 8, 7:00 PM
Unknown Object (File)
Wed, Jan 8, 1:48 PM
Unknown Object (File)
Mon, Jan 6, 2:20 PM
Subscribers

Details

Summary

PR: 277878
Approved by: jrm (mentor), otis (mentor), mikael, yasu, 0mp
Tested by: michaelo, Antti Rasinen
MFH: 2025Q1

Diff Detail

Repository
R11 FreeBSD ports repository
Lint
Lint Skipped
Unit
Tests Skipped
Build Status
Buildable 61494
Build 58378: arc lint + arc unit

Event Timeline

michaelo created this revision.

What is the rationale behind this change, please? Moreover, I guess @jrm is the best samba person in this ballroom.

What is the rationale behind this change, please? Moreover, I guess @jrm is the best samba person in this ballroom.

We don't need to have the fdescfs from Linux compat which requires the linux.ko. We can happily use the FreeBSD native fdescfs mount for Samba 4.

What is the rationale behind this change, please? Moreover, I guess @jrm is the best samba person in this ballroom.

FWIW, if I've ever run Samba, it was over 20 years ago.

It would be nice to hear from someone on samba@. Are there any open questions from bug#277878? If not, and @michaelo, if you are satisfied this is safe, I will approve.

Another question, is this applicable to net/samba416?

In D48313#1102926, @jrm wrote:

What is the rationale behind this change, please? Moreover, I guess @jrm is the best samba person in this ballroom.

FWIW, if I've ever run Samba, it was over 20 years ago.

It would be nice to hear from someone on samba@. Are there any open questions from bug#277878? If not, and @michaelo, if you are satisfied this is safe, I will approve.

I checked with truss, it works the way expected.

In D48313#1102927, @jrm wrote:

Another question, is this applicable to net/samba416?

Samba 4.16 is completely different, due to new VFS code they do not really compare, but I can check.

In D48313#1102927, @jrm wrote:

Another question, is this applicable to net/samba416?

Samba 4.16 is completely different, due to new VFS code they do not really compare, but I can check.

I have just checked, the 4.16 is affected, but already contains a reasonable patch from @timur which I'd prefer to port at some later point in time.

In D48313#1102926, @jrm wrote:

What is the rationale behind this change, please? Moreover, I guess @jrm is the best samba person in this ballroom.

FWIW, if I've ever run Samba, it was over 20 years ago.

It would be nice to hear from someone on samba@. Are there any open questions from bug#277878? If not, and @michaelo, if you are satisfied this is safe, I will approve.

I am satisfied. Regarding bug #277878, it conflates at least two different issues. This review addresses one of them. The other one is in investigation. I'd happy to commit this today.

This revision is now accepted and ready to land.Wed, Jan 8, 1:40 PM