From: Chuck Ebbert <cebbert@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Tejun Heo <htejun@gmail.com>, Kristian Hoegsberg <krh@redhat.com>,
linux-kernel@vger.kernel.org, openib-general@openib.org,
Stefan Roscher <ossrosch@linux.vnet.ibm.com>,
linuxppc-dev@ozlabs.org, raisch@de.ibm.com,
Hoang-Nam Nguyen <hnguyen@linux.vnet.ibm.com>,
jim.houston@ccur.com
Subject: Re: [PATCH] fix idr_get_new_above id alias bugs
Date: Thu, 12 Jul 2007 17:56:59 -0400 [thread overview]
Message-ID: <4696A3AB.2020602@redhat.com> (raw)
In-Reply-To: <20070712143501.2c2cdf1f.akpm@linux-foundation.org>
On 07/12/2007 05:35 PM, Andrew Morton wrote:
>>
>> With this patch, idr.c should work as advertised allocating id
>> values in the range 0...0x7fffffff. Andrew had speculated that
>> it should allow the full range 0...0xffffffff to be used. I was
>> tempted to make changes to allow this, but it would require changes
>> to API, e.g. making the starting id value and the return value
>> unsigned.
>
> Problem. There are a large number of IDR changes pending and this
> patch breaks in way which I am not at all confident in fixing.
>
> Originarily I'd just dump the earlier patches because bugfixes come
> first. But this time there's a very large dependency trail on the
> earlier patches (especially Tejun's extensive sysfs rework in Greg's
> driver tree) so the wreckage would be extensive.
>
> Also, it's possible that Tejun's changes already fixed some of the things
> which you fixed. Or added new bugs ;)
>
> Bottom line: a reworked patch against 2.6.22-rc6-mm1 would be muchly
> appreciated if poss, please.
>
> While you're there, it would be helpful if you could review all these
> pending IDR changes:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc6/2.6.22-rc6-mm1/broken-out/gregkh-driver-ida-implement-idr-based-id-allocator.patch
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc6/2.6.22-rc6-mm1/broken-out/gregkh-driver-idr-fix-obscure-bug-in-allocation-path.patch
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc6/2.6.22-rc6-mm1/broken-out/gregkh-driver-idr-separate-out-idr_mark_full.patch
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc6/2.6.22-rc6-mm1/broken-out/lib-add-idr_for_each.patch
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc6/2.6.22-rc6-mm1/broken-out/lib-add-idr_for_each-fix.patch
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc6/2.6.22-rc6-mm1/broken-out/lib-add-idr_remove_all.patch
>
The first three just got merged into mainline...
WARNING: multiple messages have this Message-ID (diff)
From: Chuck Ebbert <cebbert@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: jim.houston@ccur.com,
Hoang-Nam Nguyen <hnguyen@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
openib-general@openib.org,
Stefan Roscher <ossrosch@linux.vnet.ibm.com>,
raisch@de.ibm.com, Kristian Hoegsberg <krh@redhat.com>,
Tejun Heo <htejun@gmail.com>
Subject: Re: [PATCH] fix idr_get_new_above id alias bugs
Date: Thu, 12 Jul 2007 17:56:59 -0400 [thread overview]
Message-ID: <4696A3AB.2020602@redhat.com> (raw)
In-Reply-To: <20070712143501.2c2cdf1f.akpm@linux-foundation.org>
On 07/12/2007 05:35 PM, Andrew Morton wrote:
>>
>> With this patch, idr.c should work as advertised allocating id
>> values in the range 0...0x7fffffff. Andrew had speculated that
>> it should allow the full range 0...0xffffffff to be used. I was
>> tempted to make changes to allow this, but it would require changes
>> to API, e.g. making the starting id value and the return value
>> unsigned.
>
> Problem. There are a large number of IDR changes pending and this
> patch breaks in way which I am not at all confident in fixing.
>
> Originarily I'd just dump the earlier patches because bugfixes come
> first. But this time there's a very large dependency trail on the
> earlier patches (especially Tejun's extensive sysfs rework in Greg's
> driver tree) so the wreckage would be extensive.
>
> Also, it's possible that Tejun's changes already fixed some of the things
> which you fixed. Or added new bugs ;)
>
> Bottom line: a reworked patch against 2.6.22-rc6-mm1 would be muchly
> appreciated if poss, please.
>
> While you're there, it would be helpful if you could review all these
> pending IDR changes:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc6/2.6.22-rc6-mm1/broken-out/gregkh-driver-ida-implement-idr-based-id-allocator.patch
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc6/2.6.22-rc6-mm1/broken-out/gregkh-driver-idr-fix-obscure-bug-in-allocation-path.patch
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc6/2.6.22-rc6-mm1/broken-out/gregkh-driver-idr-separate-out-idr_mark_full.patch
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc6/2.6.22-rc6-mm1/broken-out/lib-add-idr_for_each.patch
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc6/2.6.22-rc6-mm1/broken-out/lib-add-idr_for_each-fix.patch
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc6/2.6.22-rc6-mm1/broken-out/lib-add-idr_remove_all.patch
>
The first three just got merged into mainline...
next prev parent reply other threads:[~2007-07-12 21:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 17:19 idr_get_new_above() limitation? Hoang-Nam Nguyen
2007-07-02 17:19 ` Hoang-Nam Nguyen
2007-07-02 22:56 ` Andrew Morton
2007-07-02 22:56 ` Andrew Morton
2007-07-03 0:31 ` Jim Houston
2007-07-03 0:31 ` Jim Houston
2007-07-04 14:11 ` Hoang-Nam Nguyen
2007-07-04 14:11 ` Hoang-Nam Nguyen
2007-07-10 20:05 ` [PATCH] fix idr_get_new_above id alias bugs Jim Houston
2007-07-10 20:05 ` Jim Houston
2007-07-11 19:27 ` Hoang-Nam Nguyen
2007-07-11 19:27 ` Hoang-Nam Nguyen
2007-07-12 21:35 ` Andrew Morton
2007-07-12 21:35 ` Andrew Morton
2007-07-12 21:56 ` Chuck Ebbert [this message]
2007-07-12 21:56 ` Chuck Ebbert
2007-07-13 3:46 ` Tejun Heo
2007-07-13 3:46 ` Tejun Heo
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=4696A3AB.2020602@redhat.com \
--to=cebbert@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hnguyen@linux.vnet.ibm.com \
--cc=htejun@gmail.com \
--cc=jim.houston@ccur.com \
--cc=krh@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=openib-general@openib.org \
--cc=ossrosch@linux.vnet.ibm.com \
--cc=raisch@de.ibm.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.