On 25 April 2017 at 15:16, Pablo Neira Ayuso <pablo@xxxxxxxxxxxxx> wrote:
>
> Yes, but this is going to full the logs if ever happen.
>
> Better add stats:
>
> /* statistics */
> struct {
> uint64_t msg_rcv_malformed;
> uint32_t msg_rcv_bad_version;
> uint32_t msg_rcv_bad_payload;
> uint32_t msg_rcv_bad_header;
> uint32_t msg_rcv_bad_type;
> uint32_t msg_rcv_truncated;
> uint32_t msg_rcv_bad_size;
> uint32_t msg_snd_malformed;
> uint64_t msg_rcv_lost;
> uint64_t msg_rcv_before;
> } error;
>
> A quick glance at the code to see how we're globaling deal with lack
> of memory would be good. There's little we can do in that situation,
> and in my experience this most likely point to a memory leak.
>
> So better follow a less agressive way than filling the logs, OK? We
> indeed have a way to report this via the existing -s options.
Ok, then I can drop this patch from the series and add later a couple
more of stats.
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
