public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: netdev@vger.kernel.org, kuba@kernel.org, pabeni@redhat.com,
	davem@davemloft.net, edumazet@google.com,
	xiyou.wangcong@gmail.com, victor@mojatatu.com,
	pctammela@mojatatu.com, idosch@idosch.org, mleitner@redhat.com,
	vladbu@nvidia.com, paulb@nvidia.com
Subject: Re: [patch net-next] net: sched: move block device tracking into tcf_block_get/put_ext()
Date: Thu, 4 Jan 2024 19:03:27 +0100	[thread overview]
Message-ID: <ZZby7xSkQpWHwPOA@nanopsycho> (raw)
In-Reply-To: <CAM0EoMkDhnm0QPtZEQPbnQtkfW7tTjHdv3fQoXzRXARVdhbc0A@mail.gmail.com>

Thu, Jan 04, 2024 at 05:10:58PM CET, jhs@mojatatu.com wrote:
>On Thu, Jan 4, 2024 at 7:58 AM Jiri Pirko <jiri@resnulli.us> wrote:
>>
>> From: Jiri Pirko <jiri@nvidia.com>
>>
>> Inserting the device to block xarray in qdisc_create() is not suitable
>> place to do this. As it requires use of tcf_block() callback, it causes
>> multiple issues. It is called for all qdisc types, which is incorrect.
>>
>> So, instead, move it to more suitable place, which is tcf_block_get_ext()
>> and make sure it is only done for qdiscs that use block infrastructure
>> and also only for blocks which are shared.
>>
>> Symmetrically, alter the cleanup path, move the xarray entry removal
>> into tcf_block_put_ext().
>>
>> Fixes: 913b47d3424e ("net/sched: Introduce tc block netdev tracking infra")
>> Reported-by: Ido Schimmel <idosch@nvidia.com>
>> Closes: https://lore.kernel.org/all/ZY1hBb8GFwycfgvd@shredder/
>> Reported-by: Kui-Feng Lee <sinquersw@gmail.com>
>> Closes: https://lore.kernel.org/all/ce8d3e55-b8bc-409c-ace9-5cf1c4f7c88e@gmail.com/
>> Reported-and-tested-by: syzbot+84339b9e7330daae4d66@syzkaller.appspotmail.com
>> Closes: https://lore.kernel.org/all/0000000000007c85f5060dcc3a28@google.com/
>> Reported-and-tested-by: syzbot+806b0572c8d06b66b234@syzkaller.appspotmail.com
>> Closes: https://lore.kernel.org/all/00000000000082f2f2060dcc3a92@google.com/
>> Reported-and-tested-by: syzbot+0039110f932d438130f9@syzkaller.appspotmail.com
>> Closes: https://lore.kernel.org/all/0000000000007fbc8c060dcc3a5c@google.com/
>> Signed-off-by: Jiri Pirko <jiri@nvidia.com>
>
>Did you get a chance to run the tdc tests?

I ran the TC ones we have in the net/forwarding directory.
I didn't manage to run the tdc. Readme didn't help me much.
How do you run the suite?


  reply	other threads:[~2024-01-04 18:03 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-04 12:58 [patch net-next] net: sched: move block device tracking into tcf_block_get/put_ext() Jiri Pirko
2024-01-04 14:32 ` Ido Schimmel
2024-01-04 16:10 ` Jamal Hadi Salim
2024-01-04 18:03   ` Jiri Pirko [this message]
2024-01-04 18:22     ` Jamal Hadi Salim
2024-01-05 11:24       ` Jiri Pirko
2024-01-05 11:51         ` Pedro Tammela
2024-01-06 11:14           ` Jiri Pirko
2024-01-06 11:49             ` Jamal Hadi Salim
2024-01-04 19:26 ` Victor Nogueira
2024-01-04 19:36   ` Jamal Hadi Salim
2024-01-05 11:20 ` patchwork-bot+netdevbpf
2024-01-10 12:09 ` Ido Schimmel
2024-01-10 14:08   ` Jiri Pirko
2024-01-10 16:17   ` Jiri Pirko
2024-01-11  8:51     ` Ido Schimmel
2024-01-11 15:40   ` Jamal Hadi Salim
2024-01-11 15:42     ` Jamal Hadi Salim
2024-01-11 16:17       ` Petr Machata
2024-01-11 19:55         ` Jamal Hadi Salim
2024-01-11 21:44           ` Petr Machata
2024-01-12 14:47             ` Jamal Hadi Salim
2024-01-12 15:37               ` Petr Machata
2024-01-15 21:02                 ` Jamal Hadi Salim
2024-01-16 10:15                   ` Petr Machata
2024-01-17 20:44                     ` Jamal Hadi Salim
2024-01-19 16:28                       ` Petr Machata
2024-01-21 18:32                         ` Jamal Hadi Salim
2024-01-11 16:27       ` Jiri Pirko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZZby7xSkQpWHwPOA@nanopsycho \
    --to=jiri@resnulli.us \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=idosch@idosch.org \
    --cc=jhs@mojatatu.com \
    --cc=kuba@kernel.org \
    --cc=mleitner@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=paulb@nvidia.com \
    --cc=pctammela@mojatatu.com \
    --cc=victor@mojatatu.com \
    --cc=vladbu@nvidia.com \
    --cc=xiyou.wangcong@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox