All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <srostedt@redhat.com>
To: Dave Jones <davej@redhat.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	laijs@cn.fujitsu.com, fweisbec@gmail.com, mingo@elte.hu
Subject: Re: remove unnecessary ftrace WARN_ONCE's.
Date: Fri, 20 Apr 2012 14:11:23 -0400	[thread overview]
Message-ID: <1334945483.5763.2.camel@fedora> (raw)
In-Reply-To: <20120420170356.GC2168@redhat.com>

On Fri, 2012-04-20 at 13:03 -0400, Dave Jones wrote:
> On Wed, Apr 11, 2012 at 10:31:32PM -0400, Dave Jones wrote:
>  > These warnings are trivially triggerable by any user, and serve no useful purpose afaics
>  > Just -EINVAL and be done.
>  > 
>  > Signed-off-by: Dave Jones <davej@redhat.com>
>  > 
>  > diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
>  > index ed7b5d1..a745317 100644
>  > --- a/kernel/trace/trace.c
>  > +++ b/kernel/trace/trace.c
>  > @@ -4136,13 +4136,11 @@ tracing_buffers_splice_read(struct file *file, loff_t *ppos,
>  >  		return -ENOMEM;
>  >  
>  >  	if (*ppos & (PAGE_SIZE - 1)) {
>  > -		WARN_ONCE(1, "Ftrace: previous read must page-align\n");
>  >  		ret = -EINVAL;
>  >  		goto out;
>  >  	}
>  >  
>  >  	if (len & (PAGE_SIZE - 1)) {
>  > -		WARN_ONCE(1, "Ftrace: splice_read should page-align\n");
>  >  		if (len < PAGE_SIZE) {
>  >  			ret = -EINVAL;
>  >  			goto out;
>  > --
> 
> Anyone want to pick this up, or shall I just send it to Linus myself ?

I can pick this up, if you don't mind them going in on 3.5. As they are
only WARN_ONCE errors, I don't think they are that big of a deal.

-- Steve



      reply	other threads:[~2012-04-20 18:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-12  2:31 remove unnecessary ftrace WARN_ONCE's Dave Jones
2012-04-20 17:03 ` Dave Jones
2012-04-20 18:11   ` Steven Rostedt [this message]

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=1334945483.5763.2.camel@fedora \
    --to=srostedt@redhat.com \
    --cc=davej@redhat.com \
    --cc=fweisbec@gmail.com \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.