Bug 139565 - [ipfilter] ipfilter ioctl SIOCDELST broken
Summary: [ipfilter] ipfilter ioctl SIOCDELST broken
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: Cy Schubert
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-13 10:00 UTC by Jens Kassel
Modified: 2021-04-13 02:30 UTC (History)
0 users

See Also:


Attachments
file.diff (542 bytes, patch)
2009-10-13 10:00 UTC, Jens Kassel
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Jens Kassel 2009-10-13 10:00:07 UTC
ioctl SIOCDELST always return with error "no such process".

Fix: Apply the following patch:
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2009-10-15 02:00:16 UTC
Responsible Changed
From-To: freebsd-bugs->freebsd-net

Over to maintainer(s).
Comment 2 Cy Schubert freebsd_committer freebsd_triage 2013-07-03 06:22:06 UTC
Responsible Changed
From-To: freebsd-net->cy

Mine.
Comment 3 Cy Schubert freebsd_committer freebsd_triage 2016-04-17 03:17:30 UTC
Fixed by r255332, the update from ipf 4.1.28 to 5.1.2. Checking the history of the upline code, darrenr updated this in r1.13 of ip_state.c here --> http://ipfilter.cvs.sourceforge.net/viewvc/ipfilter/ipfilter/ip_state.c?revision=1.13&view=markup.
Comment 4 Cy Schubert freebsd_committer freebsd_triage 2016-04-17 03:20:10 UTC
Re-opening. I will patch stable/9 with the patch from upline.
Comment 5 Eitan Adler freebsd_committer freebsd_triage 2018-05-28 19:48:20 UTC
batch change:

For bugs that match the following
-  Status Is In progress 
AND
- Untouched since 2018-01-01.
AND
- Affects Base System OR Documentation

DO:

Reset to open status.


Note:
I did a quick pass but if you are getting this email it might be worthwhile to double check to see if this bug ought to be closed.
Comment 6 Cy Schubert freebsd_committer freebsd_triage 2021-04-13 02:30:25 UTC
stable/9 is no longer supported and was fixed by 5.1.2 update.