public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Quentin Perret <qperret@google.com>
To: Valentin Schneider <valentin.schneider@arm.com>
Cc: kernel test robot <lkp@intel.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Aaron Lu <aaron.lwe@gmail.com>, Phil Auld <pauld@redhat.com>,
	Julien Desfossez <jdesfossez@digitalocean.com>,
	Nishanth Aravamudan <naravamudan@digitalocean.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	lkp@01.org
Subject: Re: [sched] 10e7071b2f: BUG:kernel_NULL_pointer_dereference,address
Date: Thu, 7 Nov 2019 12:15:51 +0000	[thread overview]
Message-ID: <20191107121551.GB82729@google.com> (raw)
In-Reply-To: <20191107120922.GA82729@google.com>

On Thursday 07 Nov 2019 at 12:09:22 (+0000), Quentin Perret wrote:
> sched_move_task() follows what Peter called the 'change' pattern, so I'm
> thinking this is most likely the same issue. Dropping the lock causes an
> unmitigated race between sched_move_task() and pick_next_task_dl(), so
> hilarity ensues (set_next_task() being called twice for instance).

Bah, scratch that. 10e7071b2 is clearly before the pick_next_task()
rework, so that's not it :(

Quentin

  reply	other threads:[~2019-11-07 12:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-07  9:08 [sched] 10e7071b2f: BUG:kernel_NULL_pointer_dereference,address kernel test robot
2019-11-07 11:41 ` Valentin Schneider
2019-11-07 12:09   ` Quentin Perret
2019-11-07 12:15     ` Quentin Perret [this message]
2019-11-07 12:37       ` Valentin Schneider
2019-11-07 12:43         ` Quentin Perret
2019-11-07 13:51 ` Valentin Schneider
2019-11-07 14:46   ` Peter Zijlstra

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=20191107121551.GB82729@google.com \
    --to=qperret@google.com \
    --cc=aaron.lwe@gmail.com \
    --cc=jdesfossez@digitalocean.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=lkp@intel.com \
    --cc=naravamudan@digitalocean.com \
    --cc=pauld@redhat.com \
    --cc=peterz@infradead.org \
    --cc=torvalds@linux-foundation.org \
    --cc=valentin.schneider@arm.com \
    /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