nf_conntrack/ip_conntrack disrepencies

[Amin Azez <azez@ufomechanic.net>]

in nf_conntrack_tuple.h we have:
static inline int nf_ct_tuple_src_equal(const struct nf_conntrack_tuple *t1,
                                        const struct nf_conntrack_tuple *t2)
{
        return (t1->src.u3.all[0] == t2->src.u3.all[0] &&
                t1->src.u3.all[1] == t2->src.u3.all[1] &&
                t1->src.u3.all[2] == t2->src.u3.all[2] &&
                t1->src.u3.all[3] == t2->src.u3.all[3] &&
                t1->src.u.all == t2->src.u.all &&
                t1->src.l3num == t2->src.l3num &&
                t1->dst.protonum == t2->dst.protonum);
}

In ip_conntrack_tuple.h we have:
static inline int ip_ct_tuple_src_equal(const struct ip_conntrack_tuple *t1,
                                        const struct ip_conntrack_tuple *t2)
{
        return t1->src.ip == t2->src.ip
                && t1->src.u.all == t2->src.u.all;
}


nf_conntrack compares the dst.protonum (makes sense) but the
ip_conntrack doesn't. Is there the danger of ip_conntrack selecting
wrong matching tuples sometimes? Perhaps only in the rare case where the
hashes also match (unlikely) but I thought I would point this out.

Does protonum really belong in the dst member? Correspondingly, for
nf_conntrack, does l3num really belong in src?

The final thing that troubles me is that the dst member seems to have
things unrelated, like "dir" and "protonum", why are these part of
nf_conntrack_tuple.dst and not the top level nf_conntrack_tuple struct?

Sam