All of lore.kernel.org
 help / color / mirror / Atom feed
From: Srish Srinivasan <ssrish@vmware.com>
To: stable@vger.kernel.org
Cc: gregkh@linuxfoundation.org, patches@lists.linux.dev,
	borrello@diag.uniroma1.it, peterz@infradead.org,
	pauld@redhat.com, rostedt@goodmis.org, sashal@kernel.org,
	mingo@redhat.com, linux-kernel@vger.kernel.org,
	akaher@vmware.com, vsirnapalli@vmware.com, amakhalov@vmware.com,
	tkundu@vmware.com, keerthanak@vmware.com, srinidhir@vmware.com,
	kashwindayan@vmware.com, vbrahmajosyula@vmware.com,
	Srish Srinivasan <ssrish@vmware.com>
Subject: [PATCH v4.19.y] sched/rt: pick_next_rt_entity(): check list_entry
Date: Sat, 26 Aug 2023 07:45:35 +0530	[thread overview]
Message-ID: <20230826021535.9065-1-ssrish@vmware.com> (raw)

From: Pietro Borrello <borrello@diag.uniroma1.it>

commit 7c4a5b89a0b5a57a64b601775b296abf77a9fe97 upstream.

Commit 326587b84078 ("sched: fix goto retry in pick_next_task_rt()")
removed any path which could make pick_next_rt_entity() return NULL.
However, BUG_ON(!rt_se) in _pick_next_task_rt() (the only caller of
pick_next_rt_entity()) still checks the error condition, which can
never happen, since list_entry() never returns NULL.
Remove the BUG_ON check, and instead emit a warning in the only
possible error condition here: the queue being empty which should
never happen.

Fixes: 326587b84078 ("sched: fix goto retry in pick_next_task_rt()")
Signed-off-by: Pietro Borrello <borrello@diag.uniroma1.it>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Reviewed-by: Phil Auld <pauld@redhat.com>
Reviewed-by: Steven Rostedt (Google) <rostedt@goodmis.org>
Link: https://lore.kernel.org/r/20230128-list-entry-null-check-sched-v3-1-b1a71bd1ac6b@diag.uniroma1.it
Signed-off-by: Sasha Levin <sashal@kernel.org>
[Srish: Fixes CVE-2023-1077: sched/rt: pick_next_rt_entity(): check list_entry
	     An insufficient list empty checking in pick_next_rt_entity().
	     The _pick_next_task_rt() checks pick_next_rt_entity() returns
	     NULL or not but pick_next_rt_entity() never returns NULL.
	     So, even if the list is empty, _pick_next_task_rt() continues
	     its process.]
Signed-off-by: Srish Srinivasan <ssrish@vmware.com>
---
 kernel/sched/rt.c | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/kernel/sched/rt.c b/kernel/sched/rt.c
index 9c6c3572b..394c66442 100644
--- a/kernel/sched/rt.c
+++ b/kernel/sched/rt.c
@@ -1522,6 +1522,8 @@ static struct sched_rt_entity *pick_next_rt_entity(struct rq *rq,
 	BUG_ON(idx >= MAX_RT_PRIO);

 	queue = array->queue + idx;
+	if (SCHED_WARN_ON(list_empty(queue)))
+		return NULL;
 	next = list_entry(queue->next, struct sched_rt_entity, run_list);

 	return next;
@@ -1535,7 +1537,8 @@ static struct task_struct *_pick_next_task_rt(struct rq *rq)

 	do {
 		rt_se = pick_next_rt_entity(rq, rt_rq);
-		BUG_ON(!rt_se);
+		if (unlikely(!rt_se))
+			return NULL;
 		rt_rq = group_rt_rq(rt_se);
 	} while (rt_rq);

--
2.35.6


             reply	other threads:[~2023-08-26  2:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-26  2:15 Srish Srinivasan [this message]
2023-08-27  9:12 ` [PATCH v4.19.y] sched/rt: pick_next_rt_entity(): check list_entry Greg KH

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=20230826021535.9065-1-ssrish@vmware.com \
    --to=ssrish@vmware.com \
    --cc=akaher@vmware.com \
    --cc=amakhalov@vmware.com \
    --cc=borrello@diag.uniroma1.it \
    --cc=gregkh@linuxfoundation.org \
    --cc=kashwindayan@vmware.com \
    --cc=keerthanak@vmware.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=patches@lists.linux.dev \
    --cc=pauld@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=sashal@kernel.org \
    --cc=srinidhir@vmware.com \
    --cc=stable@vger.kernel.org \
    --cc=tkundu@vmware.com \
    --cc=vbrahmajosyula@vmware.com \
    --cc=vsirnapalli@vmware.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.