public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Witbrodt <dawitbro@sbcglobal.net>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Yinghai Lu <yhlu.kernel@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jeff Garzik <jeff@garzik.org>, Tejun Heo <htejun@gmail.com>,
	Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>,
	Kernel Testers <kernel-testers@vger.kernel.org>
Subject: Re: Linux 2.6.27-rc5: System boot regression caused by commit a2bd7274b47124d2fc4dfdb8c0591f545ba749dd
Date: Fri, 29 Aug 2008 23:13:55 -0700 (PDT)	[thread overview]
Message-ID: <724017.46804.qm@web82108.mail.mud.yahoo.com> (raw)



----- Original Message ----
> From: Linus Torvalds <torvalds@linux-foundation.org>
> To: Yinghai Lu <yhlu.kernel@gmail.com>
> Cc: Rafael J. Wysocki <rjw@sisk.pl>; Linux Kernel Mailing List <linux-kernel@vger.kernel.org>; Jeff Garzik <jeff@garzik.org>; Tejun Heo <htejun@gmail.com>; Ingo Molnar <mingo@elte.hu>; David Witbrodt <dawitbro@sbcglobal.net>; Andrew Morton <akpm@linux-foundation.org>; Kernel Testers <kernel-testers@vger.kernel.org>
> Sent: Friday, August 29, 2008 10:56:50 PM
> Subject: Re: Linux 2.6.27-rc5: System boot regression caused by commit a2bd7274b47124d2fc4dfdb8c0591f545ba749dd
> 
> 
> 
> On Fri, 29 Aug 2008, Linus Torvalds wrote:
> > 
> > Yes. And I do think this is a workable model.
> 
> Ok, and here's the patch to do
> 
>     insert_resource_expand_to_fit(root, new);
> 
> and while I still haven't actually tested it, it looks sane and compiles 
> to code that also looks sane.
> 
> I'll happily commit this as basic infrastructure as soon as somebody ack's 
> it and tests that it works (and I'll try it myself soon enough, just for 
> fun)
> 
>         Linus
> 
> ---
> include/linux/ioport.h |    1 +
> kernel/resource.c      |   88 ++++++++++++++++++++++++++++++++++-------------
> 2 files changed, 64 insertions(+), 25 deletions(-)
> 
> diff --git a/include/linux/ioport.h b/include/linux/ioport.h
> index 22d2115..8d3b7a9 100644
> --- a/include/linux/ioport.h
> +++ b/include/linux/ioport.h
> @@ -109,6 +109,7 @@ extern struct resource iomem_resource;
> extern int request_resource(struct resource *root, struct resource *new);
> extern int release_resource(struct resource *new);
> extern int insert_resource(struct resource *parent, struct resource *new);
> +extern void insert_resource_expand_to_fit(struct resource *root, struct 
> resource *new);
> extern int allocate_resource(struct resource *root, struct resource *new,
>                  resource_size_t size, resource_size_t min,
>                  resource_size_t max, resource_size_t align,
> diff --git a/kernel/resource.c b/kernel/resource.c
> index f5b518e..72ee95b 100644
> --- a/kernel/resource.c
> +++ b/kernel/resource.c
> @@ -362,35 +362,21 @@ int allocate_resource(struct resource *root, struct 
> resource *new,
> 
> EXPORT_SYMBOL(allocate_resource);
> 
> -/**
> - * insert_resource - Inserts a resource in the resource tree
> - * @parent: parent of the new resource
> - * @new: new resource to insert
> - *
> - * Returns 0 on success, -EBUSY if the resource can't be inserted.
> - *
> - * This function is equivalent to request_resource when no conflict
> - * happens. If a conflict happens, and the conflicting resources
> - * entirely fit within the range of the new resource, then the new
> - * resource is inserted and the conflicting resources become children of
> - * the new resource.
> +/*
> + * Insert a resource into the resource tree. If successful, return NULL,
> + * otherwise return the conflicting resource (compare to __request_resource())
>   */
> -int insert_resource(struct resource *parent, struct resource *new)
> +static struct resource * __insert_resource(struct resource *parent, struct 
> resource *new)
> {
> -    int result;
>     struct resource *first, *next;
> 
> -    write_lock(&resource_lock);
> -
>     for (;; parent = first) {
> -         result = 0;
>         first = __request_resource(parent, new);
>         if (!first)
> -            goto out;
> +            return first;
> 
> -        result = -EBUSY;
>         if (first == parent)
> -            goto out;
> +            return first;
> 
>         if ((first->start > new->start) || (first->end < new->end))
>             break;
> @@ -401,15 +387,13 @@ int insert_resource(struct resource *parent, struct 
> resource *new)
>     for (next = first; ; next = next->sibling) {
>         /* Partial overlap? Bad, and unfixable */
>         if (next->start < new->start || next->end > new->end)
> -            goto out;
> +            return next;
>         if (!next->sibling)
>             break;
>         if (next->sibling->start > new->end)
>             break;
>     }
> 
> -    result = 0;
> -
>     new->parent = parent;
>     new->sibling = next->sibling;
>     new->child = first;
> @@ -426,10 +410,64 @@ int insert_resource(struct resource *parent, struct 
> resource *new)
>             next = next->sibling;
>         next->sibling = new;
>     }
> +    return NULL;
> +}
> 
> - out:
> +/**
> + * insert_resource - Inserts a resource in the resource tree
> + * @parent: parent of the new resource
> + * @new: new resource to insert
> + *
> + * Returns 0 on success, -EBUSY if the resource can't be inserted.
> + *
> + * This function is equivalent to request_resource when no conflict
> + * happens. If a conflict happens, and the conflicting resources
> + * entirely fit within the range of the new resource, then the new
> + * resource is inserted and the conflicting resources become children of
> + * the new resource.
> + */
> +int insert_resource(struct resource *parent, struct resource *new)
> +{
> +    struct resource *conflict;
> +
> +    write_lock(&resource_lock);
> +    conflict = __insert_resource(parent, new);
>     write_unlock(&resource_lock);
> -    return result;
> +    return conflict ? -EBUSY : 0;
> +}
> +
> +/**
> + * insert_resource_expand_to_fit - Insert a resource into the resource tree
> + * @parent: parent of the new resource
> + * @new: new resource to insert
> + *
> + * Insert a resource into the resource tree, possibly expanding it in order
> + * to make it encompass any conflicting resources.
> + */
> +void insert_resource_expand_to_fit(struct resource *root, struct resource *new)
> +{
> +    if (new->parent)
> +        return;
> +
> +    write_lock(&resource_lock);
> +    for (;;) {
> +        struct resource *conflict;
> +
> +        conflict = __insert_resource(root, new);
> +        if (!conflict)
> +            break;
> +        if (conflict == root)
> +            break;
> +
> +        /* Ok, expand resource to cover the conflict, then try again .. */
> +        if (conflict->start < new->start)
> +            new->start = conflict->start;
> +        if (conflict->end > new->end)
> +            new->end = conflict->end;
> +
> +        printk("Expanded resource %s due to conflict with %s", new->name, 
> conflict->name);
> +    }
> +    write_unlock(&resource_lock);    
> }
> 
> /**

Not sure if you wanted ME to test this, but I've been watching this
argument with Yinghai and became curious...

I updated my git tree so that I have the insert_resource_expand_to_fit()
changes, and the kernel builds fine.  Unfortunately, it hangs like all
2.6.2[67] kernels without reverting 3def3d6d... and 1e934dda... (or
without the later patches provided by Ingo and Yinghai).

Sorry if I am interfering... just wanted to inject this data, in case
it's meaningful!


Dave W.

             reply	other threads:[~2008-08-30  6:14 UTC|newest]

Thread overview: 85+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-30  6:13 David Witbrodt [this message]
2008-08-30  6:21 ` Linux 2.6.27-rc5: System boot regression caused by commit a2bd7274b47124d2fc4dfdb8c0591f545ba749dd Linus Torvalds
  -- strict thread matches above, loose matches on Subject: below --
2008-08-31  1:25 David Witbrodt
2008-08-31  2:17 ` Yinghai Lu
2008-08-30 23:29 David Witbrodt
2008-08-31  0:16 ` Yinghai Lu
2008-08-30  6:58 David Witbrodt
2008-08-28 23:26 Linux 2.6.27-rc5 Linus Torvalds
2008-08-29 17:13 ` Rafael J. Wysocki
2008-08-29 19:57   ` Linux 2.6.27-rc5: System boot regression caused by commit a2bd7274b47124d2fc4dfdb8c0591f545ba749dd Rafael J. Wysocki
2008-08-29 21:13     ` Yinghai Lu
2008-08-29 21:19       ` Yinghai Lu
2008-08-29 22:32         ` Rafael J. Wysocki
2008-08-29 22:31       ` Rafael J. Wysocki
2008-08-29 23:24         ` Yinghai Lu
2008-08-30  0:08           ` Linus Torvalds
2008-08-30  0:11             ` Yinghai Lu
2008-08-30  0:45               ` Linus Torvalds
2008-08-30  1:11                 ` Linus Torvalds
2008-08-30  1:30                   ` Yinghai Lu
2008-08-30  2:33                     ` Linus Torvalds
2008-08-30  2:56                       ` Linus Torvalds
2008-08-30  3:07                         ` Yinghai Lu
2008-08-30  3:24                           ` Linus Torvalds
2008-08-30  4:41                             ` Yinghai Lu
2008-08-30  5:02                               ` Yinghai Lu
2008-08-30  5:52                               ` Linus Torvalds
2008-08-30  6:18                                 ` Linus Torvalds
2008-08-30  8:02                                   ` Yinghai Lu
2008-08-30  5:22                             ` Yinghai Lu
2008-08-30  6:11                               ` Linus Torvalds
2008-08-30  3:15                         ` Linus Torvalds
2008-08-30  3:00                       ` Yinghai Lu
2008-08-30  3:10                         ` Linus Torvalds
2008-08-30  1:14                 ` Yinghai Lu
2008-08-30  2:16                   ` Linus Torvalds
2008-08-30  2:29                     ` Yinghai Lu
2008-08-30  0:20             ` Yinghai Lu
2008-08-30  0:27               ` Yinghai Lu
2008-08-30 13:32                 ` Rafael J. Wysocki
2008-08-30 16:05                   ` Yinghai Lu
2008-08-30 17:14                     ` Rafael J. Wysocki
2008-08-30 17:55                       ` Yinghai Lu
2008-08-30 18:11                         ` Yinghai Lu
2008-08-30 19:06                           ` Yinghai Lu
2008-08-30 19:51                             ` Rafael J. Wysocki
2008-08-30 20:10                               ` Yinghai Lu
2008-08-29 21:44     ` Linus Torvalds
2008-08-29 22:30       ` Rafael J. Wysocki
2008-08-30 17:39         ` Linus Torvalds
2008-08-30 18:07           ` Yinghai Lu
2008-08-30 18:43             ` Linus Torvalds
2008-08-30 19:10               ` Yinghai Lu
2008-08-30 19:31                 ` Linus Torvalds
2008-08-30 20:14                   ` Yinghai Lu
2008-08-30 20:38                     ` Yinghai Lu
2008-08-30 20:46                       ` Rafael J. Wysocki
2008-08-30 21:12                         ` Yinghai Lu
2008-08-30 21:13                           ` Yinghai Lu
2008-08-30 21:34                             ` Rafael J. Wysocki
2008-08-30 21:49                               ` Yinghai Lu
2008-08-31  1:10                               ` Yinghai Lu
2008-08-31 12:27                                 ` Rafael J. Wysocki
2008-08-31 17:42                                   ` Linus Torvalds
2008-08-31 17:54                                     ` Yinghai Lu
2008-08-31 18:03                                       ` Linus Torvalds
2008-08-31 21:03                                         ` Yinghai Lu
2008-09-01 17:53                                           ` Linus Torvalds
2008-08-30 22:41                     ` Linus Torvalds
2008-08-30 22:50                       ` Yinghai Lu
2008-08-30 23:28                         ` Linus Torvalds
2008-08-30 23:39                           ` Yinghai Lu
2008-08-31  0:27                             ` Yinghai Lu
2008-08-31  0:50                               ` Yinghai Lu
2008-08-31  3:00                                 ` Linus Torvalds
2008-08-31  3:53                                   ` Yinghai Lu
2008-08-31  3:58                                     ` Linus Torvalds
2008-08-31  4:12                                       ` Linus Torvalds
2008-08-30 19:14               ` Linus Torvalds
2008-08-30 19:26                 ` Yinghai Lu
2008-08-30 19:41                   ` Linus Torvalds
2008-08-30 19:48                     ` Yinghai Lu
2008-08-30 19:29                 ` Rafael J. Wysocki
2008-08-30 19:29                   ` Yinghai Lu
2008-08-30 19:20           ` Rafael J. Wysocki
2008-08-29 22:34     ` Jeff Garzik
2008-08-29 22:47       ` Rafael J. Wysocki

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=724017.46804.qm@web82108.mail.mud.yahoo.com \
    --to=dawitbro@sbcglobal.net \
    --cc=akpm@linux-foundation.org \
    --cc=htejun@gmail.com \
    --cc=jeff@garzik.org \
    --cc=kernel-testers@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rjw@sisk.pl \
    --cc=torvalds@linux-foundation.org \
    --cc=yhlu.kernel@gmail.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