From: Luis Chamberlain <mcgrof@kernel.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
fnovak@us.ibm.com, linux-modules@vger.kernel.org
Subject: Re: request_module DoS
Date: Thu, 12 May 2022 10:43:25 -0700 [thread overview]
Message-ID: <Yn1HPSvyT4kAW7I/@bombadil.infradead.org> (raw)
In-Reply-To: <87v8ub6jk1.fsf@mpe.ellerman.id.au>
On Thu, May 12, 2022 at 10:07:26PM +1000, Michael Ellerman wrote:
> Michael Ellerman <mpe@ellerman.id.au> writes:
> > Luis Chamberlain <mcgrof@kernel.org> writes:
> ...
> >
> >> Can someone try this on ppc64le system? At this point I am not convinced
> >> this issue is generic.
> >
> > Does your x86 system have at least 784 CPUs?
> >
> > I don't know where the original report came from, but the trace shows
> > "CPU 784", which would usually indicate a system with at least that many
> > CPUs.
>
> Update, apparently the report originally came from IBM, so I'll chase it
> up internally.
>
> I think you're right that there's probably no issue in the module code,
> sorry to waste your time.
It gives me testing happiness to know that may be the case :)
Luis
prev parent reply other threads:[~2022-05-12 17:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <YnXiuhdZ49pKL/dK@gondor.apana.org.au>
2022-05-07 7:10 ` request_module DoS Christophe Leroy
2022-05-07 8:02 ` Luis Chamberlain
2022-05-07 19:14 ` Luis Chamberlain
2022-05-09 1:42 ` Luis Chamberlain
[not found] ` <874k1zt0ec.fsf@mpe.ellerman.id.au>
2022-05-09 16:13 ` Luis Chamberlain
2022-05-11 16:35 ` Luis Chamberlain
2022-05-12 7:36 ` Michael Ellerman
2022-05-12 12:07 ` Michael Ellerman
2022-05-12 17:43 ` Luis Chamberlain [this message]
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=Yn1HPSvyT4kAW7I/@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=fnovak@us.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
/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;
as well as URLs for NNTP newsgroup(s).