public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <wfg@linux.intel.com>
To: Kay Sievers <kay@vrfy.org>
Cc: Yuanhan Liu <yuanhan.liu@linux.intel.com>,
	linux-kernel@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH 2/2] printk: return -EINVAL if the message len is bigger than the buf size
Date: Sat, 16 Jun 2012 21:21:24 +0800	[thread overview]
Message-ID: <20120616132124.GB12272@localhost> (raw)
In-Reply-To: <CAPXgP130QzSzPObbDedqMLc2Fw6CgzJNW56ccQeRPmZPp27JOA@mail.gmail.com>

On Sat, Jun 16, 2012 at 02:50:53PM +0200, Kay Sievers wrote:
> On Sat, Jun 16, 2012 at 6:40 AM, Yuanhan Liu
> <yuanhan.liu@linux.intel.com> wrote:
> > Just like what devkmsg_read() does, return -EINVAL if the message len is
> > bigger than the buf size, or it will trigger a segfault error.
> 
> Looks good to me.

Me too :)

Thanks,
Fengguang

  reply	other threads:[~2012-06-16 13:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-16  4:40 [PATCH 1/2] printk: use logbuf_mutex_lock to stop syslog_seq from going wild Yuanhan Liu
2012-06-16  4:40 ` [PATCH 2/2] printk: return -EINVAL if the message len is bigger than the buf size Yuanhan Liu
2012-06-16 12:50   ` Kay Sievers
2012-06-16 13:21     ` Fengguang Wu [this message]
2012-06-16 12:42 ` [PATCH 1/2] printk: use logbuf_mutex_lock to stop syslog_seq from going wild Kay Sievers
2012-06-16 12:59   ` Yuanhan Liu
2012-06-16 13:03     ` Kay Sievers
2012-06-16 13:25       ` Yuanhan Liu
2012-06-16 13:20     ` Fengguang Wu
2012-06-16 13:28       ` Yuanhan Liu
2012-06-16 15:28         ` 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=20120616132124.GB12272@localhost \
    --to=wfg@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kay@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yuanhan.liu@linux.intel.com \
    /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