From: Greg KH <gregkh@linuxfoundation.org>
To: Simon Schwartz <kern.simon@theschwartz.xyz>
Cc: rafael@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] driver core: Prevent overflow from causing infinite loops
Date: Wed, 11 Dec 2019 09:18:14 +0100 [thread overview]
Message-ID: <20191211081814.GA433262@kroah.com> (raw)
In-Reply-To: <2201ce63a2a171ffd2ed14e867875316efcf71db.camel@theschwartz.xyz>
On Tue, Dec 10, 2019 at 05:41:37PM -0500, Simon Schwartz wrote:
> num_resources in the platform_device struct is declared as a u32.
> The for loops that iterate over num_resources use an int as the counter,
> which can cause infinite loops on architectures with smaller ints.
What arch is that that has so many resources and yet is only a 32bit
system?
thanks,
greg k-h
next prev parent reply other threads:[~2019-12-11 8:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 22:41 [PATCH] driver core: Prevent overflow from causing infinite loops Simon Schwartz
2019-12-11 8:18 ` Greg KH [this message]
2019-12-20 7:51 ` [driver core] ffbb97fa23: BUG:kernel_NULL_pointer_dereference,address kernel test robot
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=20191211081814.GA433262@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=kern.simon@theschwartz.xyz \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
/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