linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hyunwoo Kim <imv4bel@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: gregory.greenman@intel.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] iwlwifi: pcie: Fixed integer overflow in iwl_write_to_user_buf
Date: Wed, 15 Jun 2022 00:45:56 -0700	[thread overview]
Message-ID: <20220615074556.GA597096@ubuntu> (raw)
In-Reply-To: <fe88188dfe37050b097803a4ce175478a794208c.camel@sipsolutions.net>

On Wed, Jun 15, 2022 at 09:06:51AM +0200, Johannes Berg wrote:
> On Tue, 2022-06-14 at 10:33 -0700, Hyunwoo Kim wrote:
> > An integer overflow occurs in the iwl_write_to_user_buf() function,
> >    which is called by the iwl_dbgfs_monitor_data_read() function.
> > 
> 
> Out of curiosity, how did you find this?

I found it while analyzing several device drivers as a personal hobby.


I also want to ask you one question.
While analyzing several device drivers, I found several such integer overflow 
or race condition problems, and made and submitted a patch.

https://marc.info/?l=linux-fbdev&m=165497564701256&w=2
https://www.spinics.net/lists/linux-efi/msg24884.html

However, there is no response whether this patch has been accepted or rejected. 
In this case, do I have to send an email to the higher level maintainer? Or do I have to wait?

Thanks,
Hyunwoo Kim

  reply	other threads:[~2022-06-15  7:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-14 17:33 [PATCH] iwlwifi: pcie: Fixed integer overflow in iwl_write_to_user_buf Hyunwoo Kim
2022-06-15  7:06 ` Johannes Berg
2022-06-15  7:45   ` Hyunwoo Kim [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-06-26 10:59 Hyunwoo Kim
2022-06-30  6:37 ` Kalle Valo

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=20220615074556.GA597096@ubuntu \
    --to=imv4bel@gmail.com \
    --cc=gregory.greenman@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.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;
as well as URLs for NNTP newsgroup(s).