mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Joe Perches <joe@perches.com>, Kay Sievers <kay@vrfy.org>
Subject: Re: [PATCH v2] drivers/base: Fix length checks in create_syslog_header()/dev_vprintk_emit()
Date: Wed, 9 Jul 2014 16:57:36 -0700	[thread overview]
Message-ID: <20140709235736.GA31914@kroah.com> (raw)
In-Reply-To: <1402267903.23860.45.camel@deadeye.wl.decadent.org.uk>

On Sun, Jun 08, 2014 at 11:51:43PM +0100, Ben Hutchings wrote:
> snprintf() returns the number of bytes that could have been written
> (excluding the null), not the actual number of bytes written.  Given a
> long enough subsystem or device name, these functions will advance
> beyond the end of the on-stack buffer in dev_vprintk_exit(), resulting
> in an information leak or stack corruption.  I don't know whether such
> a long name is currently possible.
> 
> In case snprintf() returns a value >= the buffer size, do not add
> structured logging information.  Also WARN if this happens, so we can
> fix the driver or increase the buffer size.
> 
> Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
> ---
> v2: use dev_WARN() not dev_WARN_ON()

This patch breaks the build in a huge way:

drivers/base/core.c: In function ‘create_syslog_header’:
drivers/base/core.c:2049:16: error: expected ‘)’ before numeric constant
  dev_WARN(dev, 1, "device/subsystem name too long");
                  ^

is the start of it, it goes on for a page or so after that :(

greg k-h

  parent reply	other threads:[~2014-07-09 23:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-08 22:51 Ben Hutchings
2014-06-09  2:16 ` Joe Perches
2014-07-09 23:57 ` Greg Kroah-Hartman [this message]
2014-07-11 17:20   ` Ben Hutchings
2014-07-11 18:12     ` Greg Kroah-Hartman

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=20140709235736.GA31914@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=ben@decadent.org.uk \
    --cc=joe@perches.com \
    --cc=kay@vrfy.org \
    --cc=linux-kernel@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

Powered by JetHome