All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: Pedro Tammela <pctammela@mojatatu.com>,
	markovicbudimir@gmail.com, Christian Theune <ct@flyingcircus.io>,
	stable@vger.kernel.org, netdev@vger.kernel.org,
	Linux regressions mailing list <regressions@lists.linux.dev>,
	davem@davemloft.net, edumazet@google.com, pabeni@redhat.com
Subject: Re: [REGRESSION] Userland interface breaks due to hard HFSC_FSC requirement
Date: Tue, 10 Oct 2023 11:26:47 -0700	[thread overview]
Message-ID: <20231010112647.2cd6590c@kernel.org> (raw)
In-Reply-To: <CAM0EoM=mnOdEgHPzbPxCAotoy4C54XyGiisrjwnO_raqVWPryw@mail.gmail.com>

On Tue, 10 Oct 2023 11:02:25 -0400 Jamal Hadi Salim wrote:
> > > We had a UAF with a very straight forward way to trigger it.  
> >
> > Any details?  
> 
> As in you want the sequence of commands that caused the fault posted?
> Budimir, lets wait for Jakub's response before you do that. I have
> those details as well of course.

More - the sequence of events which leads to the UAF, and on what
object it occurs. If there's an embargo or some such we can wait 
a little longer before discussing?

I haven't looked at the code for more than a minute. If this is super
trivial to spot let me know, I'll stare harder. Didn't seem like the
qdisc as a whole is all that trivial.

  parent reply	other threads:[~2023-10-10 18:26 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-06  8:37 [REGRESSION] Userland interface breaks due to hard HFSC_FSC requirement Christian Theune
2023-10-06  9:01 ` Linux regression tracking (Thorsten Leemhuis)
2023-10-06  9:07   ` Christian Theune
2023-10-06  9:16     ` Linux regression tracking (Thorsten Leemhuis)
2023-10-06 10:51       ` Christian Theune
2023-10-06 12:07         ` Bagas Sanjaya
2023-10-06 12:37           ` Christian Theune
2023-10-06 14:13             ` Bagas Sanjaya
2023-10-09 13:15               ` Christian Theune
2023-10-06 12:23     ` Florian Westphal
2023-10-06 18:51 ` Pedro Tammela
2023-10-06 22:12 ` Pedro Tammela
2023-10-07  4:10   ` Christian Theune
2023-10-09 15:06     ` Jakub Kicinski
2023-10-09 15:31       ` Pedro Tammela
2023-10-09 15:46         ` Christian Theune
2023-10-10  0:28         ` Jakub Kicinski
2023-10-10 15:02           ` Jamal Hadi Salim
2023-10-10 17:31             ` Christian Theune
2023-10-11 17:26               ` Jamal Hadi Salim
2023-10-10 18:26             ` Jakub Kicinski [this message]
2023-10-11 17:27               ` Jamal Hadi Salim
2023-10-11 18:11                 ` Christian Theune
2023-11-01 19:05 ` Linux regression tracking #update (Thorsten Leemhuis)
2023-11-02  8:05   ` Linux regression tracking #update (Thorsten Leemhuis)

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=20231010112647.2cd6590c@kernel.org \
    --to=kuba@kernel.org \
    --cc=ct@flyingcircus.io \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jhs@mojatatu.com \
    --cc=markovicbudimir@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pctammela@mojatatu.com \
    --cc=regressions@lists.linux.dev \
    --cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.