linux-kernel - Re: sched: Fix signedness bug in yield

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] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 21 Feb 2013 15:35:03 +0530
From:	Raghavendra KT <raghavendra.kt.linux@...il.com>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	Shuah Khan <shuahkhan@...il.com>,
	Marcelo Tosatti <mtosatti@...hat.com>,
	dan.carpenter@...cle.com, peterz@...radead.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	torvalds@...ux-foundation.org
Subject: Re: sched: Fix signedness bug in yield_to()

On Thu, Feb 21, 2013 at 2:26 PM, Ingo Molnar <mingo@...nel.org> wrote:
>
> * Shuah Khan <shuahkhan@...il.com> wrote:
>
>> On Tue, Feb 19, 2013 at 7:27 PM, Linux Kernel Mailing List
>> <linux-kernel@...r.kernel.org> wrote:
>> > Gitweb:     http://git.kernel.org/linus/;a=commit;h=c3c186403c6abd32e719f005f0af950155a9e54d
>> > Commit:     c3c186403c6abd32e719f005f0af950155a9e54d
>> > Parent:     e0a79f529d5ba2507486d498b25da40911d95cf6
>> > Author:     Dan Carpenter <dan.carpenter@...cle.com>
>> > AuthorDate: Tue Feb 5 14:37:51 2013 +0300
>> > Committer:  Ingo Molnar <mingo@...nel.org>
>> > CommitDate: Tue Feb 5 12:59:29 2013 +0100
>> >
>> >     sched: Fix signedness bug in yield_to()
>> >
>> >     In 7b270f6099 "sched: Bail out of yield_to when source and
>> >     target runqueue has one task" we changed this to store -ESRCH so
>> >     it needs to be signed.
>>
>> Dan, Ingo,
>>
>> I can't find the 7b270f6099 "sched: Bail out of yield_to when
>> source and target runqueue has one task" in the latest Linus's
>> git. Am I missing something.
>>
>> The current kenel/sched/core.c doesn't have the code from the
>> associated patch https://patchwork.kernel.org/patch/2016651/
>
> As per the lkml discussion that one was supposed to go upstream
> via the KVM tree. Marcelo?
>

It is going via KVM tree. (as per Gleb's pull request)
--
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/