public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Dave Jones <davej@redhat.com>,
	linux-kernel@vger.kernel.org, peterz@infradead.org,
	mingo@kernel.org, mtk.manpages@gmail.com,
	torvalds@linux-foundation.org, stable@vger.kernel.org
Subject: Re: Patch "sched: Disallow sched_attr::sched_policy < 0" has been added to the 3.14-stable tree
Date: Mon, 9 Jun 2014 12:32:16 -0700	[thread overview]
Message-ID: <20140609193216.GA28115@kroah.com> (raw)
In-Reply-To: <20140609191551.GA1422@redhat.com>

On Mon, Jun 09, 2014 at 03:15:51PM -0400, Dave Jones wrote:
> On Mon, Jun 09, 2014 at 12:07:07PM -0700, gregkh@linuxfoundation.org wrote:
>  > 
>  > This is a note to let you know that I've just added the patch titled
>  > 
>  >     sched: Disallow sched_attr::sched_policy < 0
>  > 
>  > to the 3.14-stable tree which can be found at:
>  >     http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> 
>  > --- a/kernel/sched/core.c
>  > +++ b/kernel/sched/core.c
>  > @@ -3683,6 +3683,9 @@ SYSCALL_DEFINE3(sched_setattr, pid_t, pi
>  >  	if (sched_copy_attr(uattr, &attr))
>  >  		return -EFAULT;
>  >  
>  > +	if (attr.sched_policy < 0)
>  > +		return -EINVAL;
>  > +
>  >  	rcu_read_lock();
>  >  	retval = -ESRCH;
>  >  	p = find_process_by_pid(pid);
> 
> Greg,
> 
> Make sure you also grab b14ed2c273f8ab872ae4e6735fe5ab09cb14b8c3 to fix this commit.

Ah, missed that one, thanks for pointing it out, now applied.

greg k-h

      reply	other threads:[~2014-06-09 19:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1402340827594@kroah.com>
2014-06-09 19:15 ` Patch "sched: Disallow sched_attr::sched_policy < 0" has been added to the 3.14-stable tree Dave Jones
2014-06-09 19:32   ` Greg KH [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=20140609193216.GA28115@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=peterz@infradead.org \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.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