[NETFILTER/RXRPC]: Don't use seq_release_private where inappropriate.
Some netfilter code and rxrpc one use seq_open() to open a proc file, but seq_release_private to release one. This is harmless, but ambiguous. Signed-off-by: Pavel Emelyanov <xemul@openvz.org> Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
committed by
David S. Miller
parent
c20932d2c9
commit
665bba1087
@@ -103,7 +103,7 @@ const struct file_operations rxrpc_call_seq_fops = {
|
||||
.open = rxrpc_call_seq_open,
|
||||
.read = seq_read,
|
||||
.llseek = seq_lseek,
|
||||
.release = seq_release_private,
|
||||
.release = seq_release,
|
||||
};
|
||||
|
||||
/*
|
||||
@@ -188,5 +188,5 @@ const struct file_operations rxrpc_connection_seq_fops = {
|
||||
.open = rxrpc_connection_seq_open,
|
||||
.read = seq_read,
|
||||
.llseek = seq_lseek,
|
||||
.release = seq_release_private,
|
||||
.release = seq_release,
|
||||
};
|
||||
|
Reference in New Issue
Block a user