Call for help - fixes for 19.11.x in regard to new toolchains, kernels ...

[Christian Ehrhardt]

On Tue, Dec 14, 2021 at 1:11 PM Wang, Haiyue <haiyue.wang at intel.com> wrote:
>
> Hi Christian,
>
> > -----Original Message-----
> > From: Christian Ehrhardt <christian.ehrhardt at canonical.com>
> > Sent: Tuesday, December 14, 2021 16:12
> > To: dev <dev at dpdk.org>
> > Cc: aron Conole <aconole at redhat.com>; Gujjar, Abhinandan S <abhinandan.gujjar at intel.com>; Ajit
> > Khaparde <ajit.khaparde at broadcom.com>; Akhil Goyal <gakhil at marvell.com>; Burakov, Anatoly
> > <anatoly.burakov at intel.com>; Andrew Boyer <aboyer at pensando.io>; Andrew Rybchenko
> > <andrew.rybchenko at oktetlabs.ru>; Ankur Dwivedi <adwivedi at marvell.com>; Anoob Joseph
> > <anoobj at marvell.com>; Artem V. Andreev <artem.andreev at oktetlabs.ru>; Ashish Gupta
> > <ashish.gupta at marvell.com>; Ashwin Sekhar T K <asekhar at marvell.com>; Xing, Beilei
> > <beilei.xing at intel.com>; Iremonger, Bernard <bernard.iremonger at intel.com>; Richardson, Bruce
> > <bruce.richardson at intel.com>; Marohn, Byron <byron.marohn at intel.com>; Chas Williams <chas3 at att.com>;
> > Xia, Chenbo <chenbo.xia at intel.com>; Loftus, Ciara <ciara.loftus at intel.com>; Power, Ciara
> > <ciara.power at intel.com>; Dumitrescu, Cristian <cristian.dumitrescu at intel.com>; David Christensen
> > <drc at linux.vnet.ibm.com>; Hunt, David <david.hunt at intel.com>; David Marchand
> > <david.marchand at redhat.com>; Doherty, Declan <declan.doherty at intel.com>; Jain, Deepak K
> > <deepak.k.jain at intel.com>; Devendra Singh Rawat <dsinghrawat at marvell.com>; Dmitry Kozlyuk
> > <dmitry.kozliuk at gmail.com>; Dmitry Malloy <dmitrym at microsoft.com>; Ed Czeck <ed.czeck at atomicrules.com>;
> > Carrillo, Erik G <erik.g.carrillo at intel.com>; Evgeny Schemeilin <evgenys at amazon.com>; Zhang, Roy Fan
> > <roy.fan.zhang at intel.com>; Yigit, Ferruh <ferruh.yigit at intel.com>; Trahe, Fiona
> > <fiona.trahe at intel.com>; Gaetan Rivet <grive at u256.net>; Gagandeep Singh <g.singh at nxp.com>; Guoyang
> > Zhou <zhouguoyang at huawei.com>; Guy Kaneti <guyk at marvell.com>; Guy Tzalik <gtzalik at amazon.com>; Wang,
> > Haiyue <haiyue.wang at intel.com>; Harman Kalra <hkalra at marvell.com>; Van Haaren, Harry
> > <harry.van.haaren at intel.com>; Heinrich Kuhn <heinrich.kuhn at netronome.com>; Hemant Agrawal
> > <hemant.agrawal at nxp.com>; Honnappa Nagarahalli <Honnappa.Nagarahalli at arm.com>; Hyong Youb Kim
> > <hyonkim at cisco.com>; Igor Chauskin <igorch at amazon.com>; Igor Russkikh <igor.russkikh at aquantia.com>;
> > Igor Russkikh <irusskikh at marvell.com>; Jakub Grajciar <jgrajcia at cisco.com>; Jakub Palider
> > <jpalider at marvell.com>; Jan Viktorin <viktorin at rehivetech.com>; Singh, Jasvinder
> > <jasvinder.singh at intel.com>; Jayatheerthan, Jay <jay.jayatheerthan at intel.com>; Jay Zhou
> > <jianjay.zhou at huawei.com>; Jerin Jacob <jerinj at marvell.com>; Jian Wang <jianwang at trustnetic.com>;
> > Jiawen Wu <jiawenwu at trustnetic.com>; Hu, Jiayu <jiayu.hu at intel.com>; Wu, Jingjing
> > <jingjing.wu at intel.com>; Daley, John <johndale at cisco.com>; Griffin, John <john.griffin at intel.com>;
> > Mcnamara, John <john.mcnamara at intel.com>; John Miller <john.miller at atomicrules.com>; John W. Linville
> > <linville at tuxdriver.com>; Joyce Kong <joyce.kong at arm.com>; Wiles, Keith <keith.wiles at intel.com>; Kevin
> > Traynor <ktraynor at redhat.com>; Kiran Kumar K <kirankumark at marvell.com>; Rybalchenko, Kirill
> > <kirill.rybalchenko at intel.com>; Ananyev, Konstantin <konstantin.ananyev at intel.com>; Daly, Lee
> > <lee.daly at intel.com>; Liang Ma <liangma at liangbit.com>; Lijun Ou <oulijun at huawei.com>; Liron Himi
> > <lironh at marvell.com>; Long Li <longli at microsoft.com>; Luca Boccassi <bluca at debian.org>; Maciej Czekaj
> > <mczekaj at marvell.com>; maintainers at dpdk.org; Marcin Wojtas <mw at semihalf.com>; Kovacevic, Marko
> > <marko.kovacevic at intel.com>; Martin Spinler <spinler at cesnet.cz>; Tahhan, Maryam
> > <maryam.tahhan at intel.com>; Matan Azrad <matan at nvidia.com>; mattias.ronnblom
> > <mattias.ronnblom at ericsson.com>; Peters, Matt <matt.peters at windriver.com>; Maxime Coquelin
> > <maxime.coquelin at redhat.com>; Michael Santana <maicolgabriel at hotmail.com>; Michael Shamis
> > <michaelsh at marvell.com>; Michal Krawczyk <mk at semihalf.com>; Min Hu (Connor) <humin29 at huawei.com>;
> > Nagadheeraj Rottela <rnagadheeraj at marvell.com>; Nalla Pradeep <pnalla at marvell.com>; Narcisa Ana Maria
> > Vasile <navasile at linux.microsoft.com>; Neil Horman <nhorman at tuxdriver.com>; Chautru, Nicolas
> > <nicolas.chautru at intel.com>; Nipun Gupta <nipun.gupta at nxp.com>; Nithin Dabilpuram
> > <ndabilpuram at marvell.com>; Olivier Matz <olivier.matz at 6wind.com>; Ori Kam <orika at nvidia.com>; De Lara
> > Guarch, Pablo <pablo.de.lara.guarch at intel.com>; Kadam, Pallavi <pallavi.kadam at intel.com>; Parav Pandit
> > <parav at nvidia.com>; Pavan Nikhilesh <pbhagavatula at marvell.com>; Pavel Belous
> > <pavel.belous at aquantia.com>; Mccarthy, Peter <peter.mccarthy at intel.com>; Yang, Qiming
> > <qiming.yang at intel.com>; Zhang, Qi Z <qi.z.zhang at intel.com>; Radha Mohan Chintakuntla
> > <radhac at marvell.com>; Nicolau, Radu <radu.nicolau at intel.com>; Rahul Lakkireddy
> > <rahul.lakkireddy at chelsio.com>; Rasesh Mody <rmody at marvell.com>; Raslan Darawsheh <rasland at nvidia.com>;
> > Raveendra Padasalagi <raveendra.padasalagi at broadcom.com>; Ray Kinsella <mdr at ashroe.eu>; Pattan, Reshma
> > <reshma.pattan at intel.com>; Robert Sanford <rsanford at akamai.com>; Xu, Rosen <rosen.xu at intel.com>;
> > Ruifeng Wang <ruifeng.wang at arm.com>; Sachin Saxena <sachin.saxena at oss.nxp.com>; Gobriel, Sameh
> > <sameh.gobriel at intel.com>; Satha Rao <skoteshwar at marvell.com>; Shahaf Shuler <shahafs at nvidia.com>;
> > Shahed Shaikh <shshaikh at marvell.com>; Shepard Siegel <shepard.siegel at atomicrules.com>; Shijith Thotton
> > <sthotton at marvell.com>; Somalapuram Amaranath <asomalap at amd.com>; Somnath Kotur
> > <somnath.kotur at broadcom.com>; Srikanth Jampala <jsrikanth at marvell.com>; Srisivasubramanian Srinivasan
> > <srinivasan at marvell.com>; Stephen Hemminger <sthemmin at microsoft.com>; Webster, Steven
> > <steven.webster at windriver.com>; Sunila Sahu <ssahu at marvell.com>; Sunil Kumar Kori <skori at marvell.com>;
> > Tejasree Kondoj <ktejasree at marvell.com>; Tetsuya Mukawa <mtetsuyah at gmail.com>; Thomas Monjalon
> > <thomas at monjalon.net>; Zhang, Tianfei <tianfei.zhang at intel.com>; McDaniel, Timothy
> > <timothy.mcdaniel at intel.com>; Tomasz Duszynski <tduszynski at marvell.com>; Kantecki, Tomasz
> > <tomasz.kantecki at intel.com>; Veerasenareddy Burru <vburru at marvell.com>; Viacheslav Ovsiienko
> > <viacheslavo at nvidia.com>; Vikas Gupta <vikas.gupta at broadcom.com>; Medvedkin, Vladimir
> > <vladimir.medvedkin at intel.com>; Wisam Jaddo <wisamm at nvidia.com>; Wang, Xiao W <xiao.w.wang at intel.com>;
> > Li, Xiaoyun <xiaoyun.li at intel.com>; Xiaoyun Wang <cloud.wangxiaoyun at huawei.com>; Xueming Li
> > <xuemingl at nvidia.com>; Wang, Yipeng1 <yipeng1.wang at intel.com>; Yisen Zhuang <yisen.zhuang at huawei.com>;
> > Wang, Yong <yongwang at vmware.com>; Ziyang Xuan <xuanziyang2 at huawei.com>; Zyta Szpak <zr at semihalf.com>
> > Subject: Re: Call for help - fixes for 19.11.x in regard to new toolchains, kernels ...
> >
> > On Mon, Jul 19, 2021 at 9:38 AM Christian Ehrhardt
> > <christian.ehrhardt at canonical.com> wrote:
> > >
> > > Hello everyone and maintainers in particular,
> > >
> > > I wanted to use this chance for an extra call for help before we later
> > > on this year call 19.11
> > > EOL and done. There have been a bunch of issues found in the 19.11 testing.
> > >
> > > We have had a few extra respins of 19.11.9 this time which resolved a
> > > few of them, but others are still left. They are mostly due to new
> > > toolchains and seem not to apply to 20.11 and later.
> > > But there are also no clear fixes known to me (have not come up in the
> > > discussions and not tagged for stable@) to resolve them.
> > >
> > > I have linked to the release notes in the announcement mail, but I
> > > expect only a few will scroll through to the known issues. Due to
> > > various other responsibilities and an upcoming PTO I can't spend much
> > > time before we are back in backporting-efforts for 19.11.10.
> > > Therefore I wanted to reach out explicitly for anyone willing and able
> > > to help to have a look at those issues to maybe resolve a bunch of
> > > them in 19.11.10 later on this year.
> > >
> > > The list of known issues in 19.11.9 are:
> > > - A Build issue with clang 12.0.1
> > >   https://bugs.dpdk.org/show_bug.cgi?id=745
> > > - A make build issue with Fedora 34 with GCC11
> > >   https://bugs.dpdk.org/show_bug.cgi?id=744
> > > - Meson based build issues with ICC-19.1.1
> > >   https://bugs.dpdk.org/show_bug.cgi?id=747
> > > - SUSE Linux Enterprise Server 15 SP3 fails of kni build
> > >   https://bugs.dpdk.org/show_bug.cgi?id=728
> > >   http://mails.dpdk.org/archives/stable/2021-June/031210.html)
> >
> > Since this overall topic seems to come up on every new stable release,
> > let me add a few new bugs of the same kind that got filed recently
> > (thanks test teams!)
> >
> > Of the above:
> > - 745 is fixed in 19.11.11-rc1
> > - 900 reported on 19.11.11-rc1 fixed in 19.11.11-rc2 (about to be released)
> > - 728 is fixed in 19.11.11-rc2 (about to be released)
> >
>
>
> > new:
> > https://bugs.dpdk.org/show_bug.cgi?id=901       DPDK    ethdev  dev
> >   [19.11.11-rc1] net/i40e build failure with make and clang 13
> > https://bugs.dpdk.org/show_bug.cgi?id=902       DPDK    ethdev  dev
> >   [19.11.11-rc1] net/ice build failure with make and clang 13
> > https://bugs.dpdk.org/show_bug.cgi?id=903       DPDK    ethdev  dev
> >   [19.11.11-rc1] net/ixgbe build failure with make and clang 13
>
> Just send for 19.11 stable ? Or send to main tree too ? Since main tree code
> have the same design, but no compile issue. (for meson design ?)

Hi,
if the issue is only in a DPDK stable release, but not in the main
branch then only send a patch for that with the prefix [PATCH 19.11]
to stabel at dpdk.org.
If an issue is present in the main tree too, then please send a fix
that applies to main to dev at dpdk.org and in your commit as well when
sending the mail Cc: stable at dpdk.org.

If you send it to the main release and it is accepted there, but you
know that it does not apply to a stable release.
You can either wait for the "Call for backports" when the work on the
next LTS starts or send the mail right away, again prefix [PATCH
19.11] to stabel at dpdk.org.

Details at the process are at [1]

Did that clarify all that you needed?

[1]: https://doc.dpdk.org/guides/contributing/patches.html#patch-for-stable-releases

> > > --
> > > Christian Ehrhardt
> > > Staff Engineer, Ubuntu Server
> > > Canonical Ltd
> >
> >
> >
> > --
> > Christian Ehrhardt
> > Staff Engineer, Ubuntu Server
> > Canonical Ltd



-- 
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd