public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Mateusz Guzik <mguzik@redhat.com>,
	gregkh@linuxfoundation.org, devel@driverdev.osuosl.org,
	Laurent Navet <laurent.navet@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: line6: fix possible overrun
Date: Tue, 29 Apr 2014 18:02:26 +0300	[thread overview]
Message-ID: <20140429150226.GU4963@mwanda> (raw)
In-Reply-To: <s5h38gw9or4.wl%tiwai@suse.de>

Yeah.  If this were a brand new driver then returning -EINVAL would be a
good idea.

Smatch actually warns about this code as well if you turn on the
--spammy option.  But there are too many of these kinds of warnings and
even I can't check them all so the warning is basically useless.

In a few months I will have improved the Smatch code to know that the
source string is too large so this bug could have been avoided.

regards,
dan carpenter

  reply	other threads:[~2014-04-29 15:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-26 17:09 [PATCH] staging: line6: fix possible overrun Laurent Navet
2014-04-26 20:47 ` Mateusz Guzik
2014-04-26 21:36   ` Dan Carpenter
2014-04-26 21:59     ` Mateusz Guzik
2014-04-27 17:39       ` Dan Carpenter
2014-04-27 19:05         ` Laurent Navet
2014-04-27 20:00         ` Mateusz Guzik
2014-04-27 22:44           ` Dan Carpenter
2014-04-29 14:47             ` Takashi Iwai
2014-04-29 15:02               ` Dan Carpenter [this message]
2014-04-29 15:26               ` Mateusz Guzik
2014-04-29 17:28                 ` Dan Carpenter

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=20140429150226.GU4963@mwanda \
    --to=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=laurent.navet@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mguzik@redhat.com \
    --cc=tiwai@suse.de \
    /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