Re: [PATCH] fix idr_get_new_above id alias bugs

> 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.
Hi Jim, thanks much for this patch. It should work fine as far
as I can read. Will give it a try in next couple of days.
Nam

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- [PATCH] fix idr_get_new_above id alias bugs
  - From: Jim Houston <jim.houston@ccur.com>

Prev by Date: Re: [EXT4 set 5][PATCH 1/1] expand inode i_extra_isize to support features in larger inode
Next by Date: [git pull request] scheduler updates
Previous by thread: [PATCH] fix idr_get_new_above id alias bugs
Next by thread: Re: [PATCH] fix idr_get_new_above id alias bugs
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]