[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170729091618.GF28392@breakpoint.cc>
Date: Sat, 29 Jul 2017 11:16:18 +0200
From: Florian Westphal <fw@...len.de>
To: Julia Lawall <julia.lawall@...6.fr>
Cc: Florian Westphal <fw@...len.de>,
linux-decnet-user@...ts.sourceforge.net, bhumirks@...il.com,
kernel-janitors@...r.kernel.org,
Pablo Neira Ayuso <pablo@...filter.org>,
Jozsef Kadlecsik <kadlec@...ckhole.kfki.hu>,
"David S. Miller" <davem@...emloft.net>,
netfilter-devel@...r.kernel.org, coreteam@...filter.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] constify nf_hook_ops structures
Julia Lawall <julia.lawall@...6.fr> wrote:
>
>
> On Sat, 29 Jul 2017, Florian Westphal wrote:
>
> > Julia Lawall <Julia.Lawall@...6.fr> wrote:
> > > The nf_hook_ops structure is only passed as the second argument to
> > > nf_register_net_hook or nf_unregister_net_hook, both of which are
> > > declared as const. Thus the nf_hook_ops structure itself can be
> > > const.
> >
> > Right, also see
> > http://patchwork.ozlabs.org/patch/793767/
> >
> > This series misses most of them (all arrays perhaps)?
>
> Yes, my rule doesn't look for arrays. I guess they are all done already
> anyway?
I think so (the patch is not yet applied though).
>From a quick glance I don't see why we can't e.g. constify
nf_conntrack_l3/4_proto too. It is not going to be as simple
as just placing const everywhere, but I see no requirement for
having these writeable.
Powered by blists - more mailing lists