mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dave Airlie" <airlied@gmail.com>
To: "Manfred Spraul" <manfred@colorfullife.com>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
	cebbert@redhat.com, akpm@linux-foundation.org
Subject: Re: [PATCH] lib/idr.c: Fix bug introduced by RCU fix
Date: Thu, 11 Dec 2008 09:46:12 +1000	[thread overview]
Message-ID: <21d7e9970812101546n40ba9043r8fdf35b986c5d377@mail.gmail.com> (raw)
In-Reply-To: <200812101729.mBAHTGdr008642@mail.q-ag.de>

On Thu, Dec 11, 2008 at 3:17 AM, Manfred Spraul
<manfred@colorfullife.com> wrote:
> The last patch to lib/idr.c caused a bug if idr_get_new_above() was
> called on an empty idr:
> Usually, nodes stay on the same layer. New layers are added to the top
> of the tree.
> The exception is idr_get_new_above() on an empty tree: In this case,
> the new root node is first added on layer 0, then moved upwards.
> p->layer was not updated.
>
> As usual: You shall never rely on the source code comments, they
> will only mislead you.
>
> Signed-off-by: Manfred Spraul <manfred@colorfullife.com>

I've given this a run on my dri system and it appears to work great.

Tested-by: Dave Airlie <airlied@redhat.com>


> ---
>  lib/idr.c |    8 +++++++-
>  1 files changed, 7 insertions(+), 1 deletions(-)
>
> diff --git a/lib/idr.c b/lib/idr.c
> index 7a785a0..1c4f928 100644
> --- a/lib/idr.c
> +++ b/lib/idr.c
> @@ -220,8 +220,14 @@ build_up:
>         */
>        while ((layers < (MAX_LEVEL - 1)) && (id >= (1 << (layers*IDR_BITS)))) {
>                layers++;
> -               if (!p->count)
> +               if (!p->count) {
> +                       /* special case: if the tree is currently empty,
> +                        * then we grow the tree by moving the top node
> +                        * upwards.
> +                        */
> +                       p->layer++;
>                        continue;
> +               }
>                if (!(new = get_from_free_list(idp))) {
>                        /*
>                         * The allocation failed.  If we built part of
> --
> 1.5.6.5
>
>

      parent reply	other threads:[~2008-12-10 23:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-10 17:17 Manfred Spraul
2008-12-10 17:39 ` Linus Torvalds
2008-12-10 23:46 ` Dave Airlie [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=21d7e9970812101546n40ba9043r8fdf35b986c5d377@mail.gmail.com \
    --to=airlied@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=cebbert@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    --cc=torvalds@linux-foundation.org \
    /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®