[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251119112522.dcfrh6x6msnw4cmi@skbuf>
Date: Wed, 19 Nov 2025 13:25:22 +0200
From: Vladimir Oltean <vladimir.oltean@....com>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: Jakub Kicinski <kuba@...nel.org>, netdev@...r.kernel.org,
Andrew Lunn <andrew@...n.ch>,
Heiner Kallweit <hkallweit1@...il.com>,
Russell King <linux@...linux.org.uk>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>,
linux-kernel@...r.kernel.org, Serge Semin <fancer.lancer@...il.com>,
Herve Codina <herve.codina@...tlin.com>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, devicetree@...r.kernel.org
Subject: Re: [PATCH net-next 14/15] net: dsa: sja1105: replace mdiobus-pcs
with xpcs-plat driver
On Wed, Nov 19, 2025 at 12:31:27PM +0200, Andy Shevchenko wrote:
> On Wed, Nov 19, 2025 at 11:59:42AM +0200, Vladimir Oltean wrote:
> > On Tue, Nov 18, 2025 at 04:41:30PM -0800, Jakub Kicinski wrote:
> > > On Tue, 18 Nov 2025 21:05:29 +0200 Vladimir Oltean wrote:
>
> ...
>
> > > > + for_each_child_of_node(node, child) {
> > > > + if (!of_node_name_eq(child, name))
> > > > + continue;
> > > > +
> > > > + if (of_property_read_u32_array(child, "reg", reg, ARRAY_SIZE(reg)))
> > > > + continue;
> > > > +
> > > > + if (reg[0] == res->start && reg[1] == resource_size(res))
> > > > + return true;
> > >
> > > coccicheck says you're likely leaking the reference on the child here
> >
> > Ok, one item added to the change list for v2.
>
> Note, we have __free() and _scoped() variants of the respective APIs to make it
> easier to not forget.
Ok, I'll use for_each_child_of_node_scoped(), as it's a good fit, thanks.
> > Why is cocci-check.sh part of the "contest" test suite that runs on
> > remote executors? This test didn't run when I tested this series locally
> > with ingest_mdir.py.
>
> I believe it's due to heavy load it makes. Running it on a (whole) kernel make
> take hours.
For context, the "local" NIPA tests for this set took me 3 hours and 34 minutes
to run on 32 AMD EPYC 9R14 CPU cores. So if cocci-check.sh increases that time
by a few additional hours, yeah, it's bad, but it was bad before too, so
the "heavy load" argument doesn't satisfactorily explain things.
Plus, looking deeper at the NIPA code, it only submits the patch set
under test to a "contest" branch if it already passed the slow
gate_checks=build_clang,build_32bit,build_allmodconfig_warn. So it's not
like the "local" build tests run in parallel with the remote worker, and
we're not saving any time for a single build.
I think it's due to the fact that the "contest" checks are fundamentally
so slow, that they can't be run on individual patch sets, and are run on
batches of patch sets merged into a single branch (of which there seem
to be 8 per day). I didn't get this from NIPA documentation, though.
Powered by blists - more mailing lists