[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <e4f32537-bec5-3d9e-11b1-0aa79fa10103@leemhuis.info>
Date: Tue, 29 Aug 2023 14:11:38 +0200
From: "Linux regression tracking #update (Thorsten Leemhuis)"
<regressions@...mhuis.info>
To: Linux Regressions <regressions@...ts.linux.dev>
Cc: Linux Xen <xen-devel@...ts.xenproject.org>,
Linux BPF <bpf@...r.kernel.org>,
Linux Networking <netdev@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Fwd: UBSAN: index 1 is out of range for type
'xen_netif_rx_sring_entry [1]'
[TLDR: This mail in primarily relevant for Linux kernel regression
tracking. See link in footer if these mails annoy you.]
On 26.07.23 07:06, Kees Cook wrote:
> On Tue, Jul 25, 2023 at 03:34:26PM +0200, Juergen Gross wrote:
>> On 25.07.23 15:24, Juergen Gross wrote:
>>> On 23.07.23 02:06, Nathan Chancellor wrote:
>>>> On Sat, Jul 22, 2023 at 07:21:05AM +0700, Bagas Sanjaya wrote:
>>>>>
>>>>> I notice a regression report on Bugzilla [1]. Quoting from it:
>>>>>>
>>>>>> I rebuild today latest version from mainline repo.
>>>>>> And i notice issue regarding xen-netfront.c.
> [...]
>> Oh, in fact there is a way in Xen to do that correctly. It schould be enough to
>> use ring[XEN_FLEX_ARRAY_DIM], which will do the right thing.
>>
>> So I'll write a Xen patch first, after all.
>
> Perfect! I went to go look, and yes, this is good:
#regzbot resolve: will be dealt with on the xen side
#regzbot ignore-activity
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
Powered by blists - more mailing lists