mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Raistlin <raistlin@linux.it>
Cc: Michael Trimarchi <trimarchimichael@yahoo.it>,
	PeterZijlstra <peterz@infradead.org>, "Daniel K." <dk@uw.no>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: divide error trying to set rt_period to zero
Date: Tue, 1 Jul 2008 08:26:04 +0200	[thread overview]
Message-ID: <20080701062604.GB16642@elte.hu> (raw)
In-Reply-To: <1214499251.10344.7.camel@Palanthas.Krynn>


* Raistlin <raistlin@linux.it> wrote:

> Ops! :-O
> 
> My fault, moving the 'if' back and forth from one function to another 
> I finally sent the wrong (and broken!) version of the patch... Very 
> sorry about it!
> 
> I know, I would have noticed just looking at the code... But I missed 
> it. :-(

hey, no problem.

> Anyway, if still interested in, the following one build and work... 
> I've just tried it and I'm quite sure this time. :-P

applied to tip/sched/urgent - thanks Dario. We are interested in it of 
course, you fixed a real bug in the scheduler :-)

small sidenote:

> +++ b/kernel/sched.c
> @@ -8501,6 +8501,9 @@ int sched_group_set_rt_period(struct task_group
> *tg, long rt_period_us)
>         rt_period = (u64)rt_period_us * NSEC_PER_USEC;
>         rt_runtime = tg->rt_bandwidth.rt_runtime;
>  
> +       if (rt_period == 0)
> +               return -EINVAL;
> +
>         return tg_set_bandwidth(tg, rt_period, rt_runtime);
>  }

that patch was whitespace damaged (lines wrapped and tabs converted to 
spaces). I fixed it up by hand - you can avoid such problems with future 
patches by sending patches a'la Documentation/email-clients.txt.

	Ingo

      reply	other threads:[~2008-07-01  6:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-25 22:17 Dario Faggioli
2008-06-26 13:39 ` Ingo Molnar
2008-06-26 16:54   ` Raistlin
2008-07-01  6:26     ` Ingo Molnar [this message]

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=20080701062604.GB16642@elte.hu \
    --to=mingo@elte.hu \
    --cc=dk@uw.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=raistlin@linux.it \
    --cc=trimarchimichael@yahoo.it \
    /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

all inboxes | Powered by JetHome®