From: Simon Horman <horms@kernel.org>
To: Manivannan Sadhasivam <mani@kernel.org>
Cc: "Jakub Kicinski" <kuba@kernel.org>,
"Łukasz Patron" <priv.luk@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Paolo Abeni" <pabeni@redhat.com>,
linux-arm-msm@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: qrtr: ns: Raise lookup limit to 128
Date: Fri, 7 Aug 2026 10:46:11 +0100 [thread overview]
Message-ID: <20260807094611.GH51943@horms.kernel.org> (raw)
In-Reply-To: <oqknkvlljjxfo5stpc3yicqzgs6g4an6lg7ybrll4zyvxr675q@hm23pe4cpxhm>
On Thu, Aug 06, 2026 at 06:00:23PM +0200, Manivannan Sadhasivam wrote:
> On Thu, Aug 06, 2026 at 07:27:02AM -0700, Jakub Kicinski wrote:
> > On Thu, 6 Aug 2026 15:38:22 +0200 Łukasz Patron wrote:
> > > After merging v6.6.142 into a downstream AOSP device, it's stuck on
> > > boot animation and following log spam can be observed in dmesg:
> > >
> > > E qrtr : ctrl_cmd_new_lookup(): QRTR client node exceeds max lookup limit!
> > > E qrtr : qrtr_ns_worker(): failed while handling packet from 1:16600
> > >
> > > No idea why it needs more than 64 client lookups, but it appears to
> > > work fine with 128 as it did when there were no limits.
> >
> > Ack, I'll fold the explanation into the commit msg. pls don't repost.
>
> With the added info,
>
> Reviewed-by: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>
Likewise,
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2026-08-07 9:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 20:18 [PATCH] net: qrtr: ns: Raise lookup limit to 128 Łukasz Patron
2026-08-06 13:26 ` Simon Horman
2026-08-06 13:38 ` Łukasz Patron
2026-08-06 14:27 ` Jakub Kicinski
2026-08-06 16:00 ` Manivannan Sadhasivam
2026-08-07 9:46 ` Simon Horman [this message]
2026-08-06 15:20 ` patchwork-bot+netdevbpf
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=20260807094611.GH51943@horms.kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mani@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=priv.luk@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox