Steven Rostedt <rost...@goodmis.org> wrote:
> From: "Steven Rostedt (Red Hat)" <rost...@goodmis.org>
> 
> [ REQUEST FOR ACKS ]
> 
> The seq_printf() and friends are having their return values removed.
> The print_conntrack() returns the result of seq_printf(), which is
> meaningless when seq_printf() returns void. Might as well remove the
> return values of print_conntrack() as well.
[..]

> diff --git a/net/ipv4/netfilter/nf_conntrack_l3proto_ipv4_compat.c 
> b/net/ipv4/netfilter/nf_conntrack_l3proto_ipv4_compat.c
> index 4c48e434bb1f..91f207c2cb69 100644
> --- a/net/ipv4/netfilter/nf_conntrack_l3proto_ipv4_compat.c
> +++ b/net/ipv4/netfilter/nf_conntrack_l3proto_ipv4_compat.c
> @@ -147,7 +147,10 @@ static int ct_seq_show(struct seq_file *s, void *v)
>                     ? (long)(ct->timeout.expires - jiffies)/HZ : 0) != 0)
>               goto release;
>  
> -     if (l4proto->print_conntrack && l4proto->print_conntrack(s, ct))
> +     if (l4proto->print_conntrack)
> +             l4proto->print_conntrack(s, ct);
> +
> +     if (seq_has_overflowed(s))
>               goto release;

Its not obvious to me why nf_conntrack_l3proto_ipv4_compat now calls
seq_has_overflowed ...

> > diff --git a/net/netfilter/nf_conntrack_standalone.c 
> > b/net/netfilter/nf_conntrack_standalone.c
> index cf65a1e040dd..348aa3602787 100644
> --- a/net/netfilter/nf_conntrack_standalone.c
> +++ b/net/netfilter/nf_conntrack_standalone.c
> @@ -199,8 +199,8 @@ static int ct_seq_show(struct seq_file *s, void *v)
>                      ? (long)(ct->timeout.expires - jiffies)/HZ : 0) != 0)
>               goto release;
>  
> -     if (l4proto->print_conntrack && l4proto->print_conntrack(s, ct))
> -             goto release;
> +     if (l4proto->print_conntrack)
> +             l4proto->print_conntrack(s, ct);
>  
>       if (print_tuple(s, &ct->tuplehash[IP_CT_DIR_ORIGINAL].tuple,
>                       l3proto, l4proto))

... while nf_conntrack_standalone does not.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to