lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8e52b826-c5b6-e144-b292-f7184d45f577@gmail.com>
Date:   Wed, 10 Jan 2018 09:17:28 -0700
From:   David Ahern <dsahern@...il.com>
To:     Jiri Pirko <jiri@...nulli.us>, netdev@...r.kernel.org
Cc:     davem@...emloft.net, jhs@...atatu.com, xiyou.wangcong@...il.com,
        mlxsw@...lanox.com, andrew@...n.ch,
        vivien.didelot@...oirfairelinux.com, f.fainelli@...il.com,
        michael.chan@...adcom.com, ganeshgr@...lsio.com,
        saeedm@...lanox.com, matanb@...lanox.com, leonro@...lanox.com,
        idosch@...lanox.com, jakub.kicinski@...ronome.com,
        simon.horman@...ronome.com, pieter.jansenvanvuuren@...ronome.com,
        john.hurley@...ronome.com, alexander.h.duyck@...el.com,
        ogerlitz@...lanox.com, john.fastabend@...il.com,
        daniel@...earbox.net
Subject: Re: [patch net-next v7 03/13] net: sched: avoid usage of tp->q in
 tcf_classify

On 1/9/18 7:07 AM, Jiri Pirko wrote:
> From: Jiri Pirko <jiri@...lanox.com>
> 
> Use block index in the messages instead.
> 
> Signed-off-by: Jiri Pirko <jiri@...lanox.com>
> ---
>  net/sched/cls_api.c | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/net/sched/cls_api.c b/net/sched/cls_api.c
> index 9b45950..31e91dc 100644
> --- a/net/sched/cls_api.c
> +++ b/net/sched/cls_api.c
> @@ -672,8 +672,9 @@ int tcf_classify(struct sk_buff *skb, const struct tcf_proto *tp,
>  #ifdef CONFIG_NET_CLS_ACT
>  reset:
>  	if (unlikely(limit++ >= max_reclassify_loop)) {
> -		net_notice_ratelimited("%s: reclassify loop, rule prio %u, protocol %02x\n",
> -				       tp->q->ops->id, tp->prio & 0xffff,
> +		net_notice_ratelimited("%u: reclassify loop, rule prio %u, protocol %02x\n",

if you are dumping index instead of prio shouldn't the 'rule prio' above
be adjusted?


> +				       tp->chain->block->index,
> +				       tp->prio & 0xffff,
>  				       ntohs(tp->protocol));
>  		return TC_ACT_SHOT;
>  	}
> 

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ