Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
L
linux
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
linux
Commits
34927f41
Commit
34927f41
authored
Sep 26, 2004
by
David S. Miller
Committed by
David S. Miller
Sep 26, 2004
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
[NET]: Remove INCOMPLETE checks from neigh_forced_gc().
Signed-off-by:
David S. Miller
<
davem@davemloft.net
>
parent
fb851470
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
3 additions
and
11 deletions
+3
-11
net/core/neighbour.c
net/core/neighbour.c
+3
-11
No files found.
net/core/neighbour.c
View file @
34927f41
...
...
@@ -123,20 +123,12 @@ static int neigh_forced_gc(struct neigh_table *tbl)
np
=
&
tbl
->
hash_buckets
[
i
];
while
((
n
=
*
np
)
!=
NULL
)
{
/* Neighbour record may be discarded if:
- nobody refers to it.
- it is not permanent
- (NEW and probably wrong)
INCOMPLETE entries are kept at least for
n->parms->retrans_time, otherwise we could
flood network with resolution requests.
It is not clear, what is better table overflow
or flooding.
* - nobody refers to it.
* - it is not permanent
*/
write_lock
(
&
n
->
lock
);
if
(
atomic_read
(
&
n
->
refcnt
)
==
1
&&
!
(
n
->
nud_state
&
NUD_PERMANENT
)
&&
(
n
->
nud_state
!=
NUD_INCOMPLETE
||
time_after
(
jiffies
,
n
->
used
+
n
->
parms
->
retrans_time
)))
{
!
(
n
->
nud_state
&
NUD_PERMANENT
))
{
*
np
=
n
->
next
;
n
->
dead
=
1
;
shrunk
=
1
;
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment