linux-kernel - Re: current->sched_class->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] [day] [month] [year] [list]

Message-ID: <CAF1ivSbqxNAiZw3RNS+BgeQJMVJeUJoCNYCbeeLAYYqG7KNxkw@mail.gmail.com>
Date:	Sat, 19 Apr 2014 09:58:41 -0700
From:	Lin Ming <minggr@...il.com>
To:	Paul Gortmaker <paul.gortmaker@...driver.com>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: current->sched_class->yield_task is NULL, any hint?

On Sat, Apr 19, 2014 at 9:21 AM, Paul Gortmaker
<paul.gortmaker@...driver.com> wrote:
> On Wed, Apr 9, 2014 at 5:39 PM, Lin Ming <minggr@...il.com> wrote:
>> On Wed, Apr 9, 2014 at 1:08 PM, Peter Zijlstra <peterz@...radead.org> wrote:
>
> [...]
>
>>>>
>>>> Look at that, its calling yield() from a non-preemptible context as
>>>> well.
>>>>
>>>> That code is full of fail.
>>>
>>> *phew* none of that br_igmp_* muck lives in any kernel tree near me so I
>>> can stop worrying :-)
>>
>> It's our internal code.
>
> In the future, please don't simply call it 3.4-rt when there are a bunch of
> vendor/project/SDK patches also applied, as that can be very misleading
> to the people you are asking for help from.  If it is a hybrid franken-kernel
> then please at least indicate that right at the very beginning.

Sorry for the misleading.
I'll make it clear next time.

Thanks.

>
> Paul.
> --
>
>>
>>>
>>> In any case, it wrongly passes a GFP_WAIT along to netlink_broadcast.
>>
>> I'll fix it.
>> Thanks very much.
--
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/