From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Jay Fenlason <fenlason@redhat.com>
Cc: linux1394-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: idr: IDs guaranteed to be less than 1<<31? (was Re: [PATCH] firewire: us an idr rather than a linked list for resources)
Date: Mon, 24 Nov 2008 20:09:01 +0100 [thread overview]
Message-ID: <492AFBCD.2020009@s5r6.in-berlin.de> (raw)
In-Reply-To: <20081124163728.GA5826@redhat.com>
Jay Fenlason wrote at linux1394-devel:
> As mentioned in the comments, there is a theoretical problem with this
> code if someone manages to allocate 2^31 resources on a 32-bit
> machine, or 2^32+1 resources on a 64+-bit machine.
The kerneldoc of idr_get_new() says that we only get IDs in the range of
0...0x7fffffff. But is this true with 64bit kernels?
--
Stefan Richter
-=====-==--- =-== ==---
http://arcgraph.de/sr/
next parent reply other threads:[~2008-11-24 19:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20081124163728.GA5826@redhat.com>
2008-11-24 19:09 ` Stefan Richter [this message]
[not found] ` <492AEED8.9030102@s5r6.in-berlin.de>
[not found] ` <492AEF9D.5010307@s5r6.in-berlin.de>
2008-12-14 18:17 ` [PATCH 0/4] firewire: cdev resources and events Stefan Richter
2008-12-14 18:19 ` [PATCH 1/4] firewire: cdev: fix race of fw_device_op_release with bus reset Stefan Richter
2008-12-14 18:20 ` [PATCH 2/4] firewire: cdev: use an idr rather than a linked list for resources Stefan Richter
2008-12-18 22:43 ` Stefan Richter
2008-12-18 23:05 ` Stefan Richter
2008-12-21 15:47 ` [PATCH 2/4 update] " Stefan Richter
2008-12-14 18:21 ` [PATCH 3/4] firewire: cdev: address handler input validation Stefan Richter
2008-12-14 18:21 ` [PATCH 4/4] firewire: core: remove outdated comment Stefan Richter
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=492AFBCD.2020009@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=fenlason@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
/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.