linux-kernel - Re: Patch "sched: Disallow sched_attr::sched_policy < 0" has been added to the 3.14-stable tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20140609193216.GA28115@kroah.com>
Date:	Mon, 9 Jun 2014 12:32:16 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Dave Jones <davej@...hat.com>, linux-kernel@...r.kernel.org,
	peterz@...radead.org, mingo@...nel.org, mtk.manpages@...il.com,
	torvalds@...ux-foundation.org, stable@...r.kernel.org
Subject: Re: Patch "sched: Disallow sched_attr::sched_policy < 0" has been
 added to the 3.14-stable tree

On Mon, Jun 09, 2014 at 03:15:51PM -0400, Dave Jones wrote:
> On Mon, Jun 09, 2014 at 12:07:07PM -0700, gregkh@...uxfoundation.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/