netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 215599] New: System freeze after add mirror rule from traffic control
Date: Mon, 14 Feb 2022 09:39:39 -0800	[thread overview]
Message-ID: <20220214093939.3874f25a@hermes.local> (raw)



Begin forwarded message:

Date: Sat, 12 Feb 2022 21:16:42 +0000
From: bugzilla-daemon@kernel.org
To: stephen@networkplumber.org
Subject: [Bug 215599] New: System freeze after add mirror rule from traffic control


https://bugzilla.kernel.org/show_bug.cgi?id=215599

            Bug ID: 215599
           Summary: System freeze after add mirror rule from traffic
                    control
           Product: Networking
           Version: 2.5
    Kernel Version: 5.16.5-arch1-1
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Other
          Assignee: stephen@networkplumber.org
          Reporter: ne-vlezay80@yandex.ru
        Regression: No

The rule:
tc qdisc add dev eth1 handle ffff: ingress
tc filter add dev eth1 parent 1: flower src_mac 22:22:22:22:22:22 action mirred
ingress mirror dev gretap-test0

System freezes after creating the rule from container.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2022-02-14 17:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-14 17:39 Stephen Hemminger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-02-14 17:30 Fw: [Bug 215599] New: System freeze after add mirror rule from traffic control Stephen Hemminger

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=20220214093939.3874f25a@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=netdev@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).