From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id AD640225C3; Tue, 10 Oct 2023 18:26:48 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="O8OGieC9" Received: by smtp.kernel.org (Postfix) with ESMTPSA id DD92CC433C8; Tue, 10 Oct 2023 18:26:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1696962408; bh=waPUWbJO/Xc9axF8eteOesPuRUq2mKO6nYwd8+mSl7o=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=O8OGieC9iXJ/DbcIGSQBJU99kCIt8X7lAt2kGPnXYquud7uIc+imEF23bTwKr17wd FjX5ceLbQc/CSEaNpU0uCVhdPzfsQcVVqapazg3mrL9UrrHUARJ2Bja/PMRQ7NkAqe ozeuOSFmo8TBfB2My9xSzLgGp2jGv7kuXderYCbd0pc+ulR1O+zLDg5vmpBtfqLBEP cmQnlT+0Z12rm+0/xkI8bz/w79q2QDxuJUNGoi/ZR48kWJIbwjuwrHSE66JE4UMCTs Lp0LTv71EPv+A6oE4mM/wIWLKc4H4nVTxReeAc/0iSUJEQ6MaaYmEcoRKCmh+eCDRo VwNRrguM5H3Yg== Date: Tue, 10 Oct 2023 11:26:47 -0700 From: Jakub Kicinski To: Jamal Hadi Salim Cc: Pedro Tammela , markovicbudimir@gmail.com, Christian Theune , stable@vger.kernel.org, netdev@vger.kernel.org, Linux regressions mailing list , davem@davemloft.net, edumazet@google.com, pabeni@redhat.com Subject: Re: [REGRESSION] Userland interface breaks due to hard HFSC_FSC requirement Message-ID: <20231010112647.2cd6590c@kernel.org> In-Reply-To: References: <297D84E3-736E-4AB4-B825-264279E2043C@flyingcircus.io> <065a0dac-499f-7375-ddb4-1800e8ef61d1@mojatatu.com> <0BC2C22C-F9AA-4B13-905D-FE32F41BDA8A@flyingcircus.io> <20231009080646.60ce9920@kernel.org> <20231009172849.00f4a6c5@kernel.org> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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.