Page MenuHomeFreeBSD

pf: use M_WAITOK where possible
ClosedPublic

Authored by kp on Jun 9 2021, 5:00 PM.
Tags
None
Referenced Files
F105275188: D30702.diff
Sat, Dec 14, 8:50 AM
Unknown Object (File)
Thu, Dec 12, 9:34 AM
Unknown Object (File)
Wed, Dec 4, 1:00 PM
Unknown Object (File)
Tue, Nov 26, 9:15 AM
Unknown Object (File)
Tue, Nov 19, 5:07 PM
Unknown Object (File)
Nov 13 2024, 2:01 PM
Unknown Object (File)
Oct 31 2024, 5:28 PM
Unknown Object (File)
Oct 27 2024, 5:08 PM

Details

Summary

In the ioctl path use M_WAITOK allocations whereever possible. These are
less sensitive to memory pressure, and ioctl requests have no hard
deadlines.

MFC after: 1 week
Sponsored by: Rubicon Communications, LLC ("Netgate")

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 39823
Build 36712: arc lint + arc unit

Event Timeline

kp requested review of this revision.Jun 9 2021, 5:00 PM
sys/netpfil/pf/pf_ioctl.c
3774–3775

These NULL checks are dead code now with M_WAITOK.

Assume you meant to include only the sys/netpfil/pf/pf_ioctl.c changes?

Assume you meant to include only the sys/netpfil/pf/pf_ioctl.c changes?

Gha, yes. I had a few local, uncommitted, changes, and apparently git-arc picked those up as well. And then helpfully removed them from my tree.

  • Remove unrelated changes
  • Don't check for NULL after M_WAITOK
donner added a subscriber: donner.

As far as I can check, all those changes are outside of the hold lock, so this is fine.

This revision is now accepted and ready to land.Jun 9 2021, 7:21 PM
This revision was automatically updated to reflect the committed changes.