From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Kyle McMartin <kyle@mcmartin.ca>
Cc: Ben Hutchings <ben@decadent.org.uk>,
linux-parisc@vger.kernel.org, Ryan Niebur <ryan@debian.org>
Subject: Re: Unexpected behaviour of idr_get_empty_slot() on parisc
Date: Mon, 18 Jan 2010 11:12:52 -0600 [thread overview]
Message-ID: <1263834772.2773.63.camel@mulgrave.site> (raw)
In-Reply-To: <1263572785.2842.28.camel@mulgrave.site>
On Fri, 2010-01-15 at 10:26 -0600, James Bottomley wrote:
> On Sun, 2010-01-03 at 18:50 -0500, Kyle McMartin wrote:
> > On Sun, Jan 03, 2010 at 11:23:25PM +0000, Ben Hutchings wrote:
> > > Ryan Niebur reported in <http://bugs.debian.org/561880> that on a
> > > PA-RISC system running Linux 2.6.32 the following test case for inotify:
> > >
> >
> > I bet this is because classic RCU is removed, and tree RCU was
> > insufficiently tested on crap platforms before the removal.
> >
> > I'll try to re-add it and we can see if it's an RCU problem or something
> > nastier.
>
> Apparently it's a feature of kernels beyond 2.6.30 (this exact
> behaviour). Suspect the bug report is incomplete and the i386 machine
> was running 2.6.29 or lower.
>
> Red Hat has been getting complaints about it so they're looking to
> revert to the old 2.6.29 behaviour as well. The actual commit that
> caused the behaviour change is
>
> commit 63c882a05416e18de6fb59f7dd6da48f3bbe8273
> Author: Eric Paris <eparis@redhat.com>
> Date: Thu May 21 17:02:01 2009 -0400
>
> inotify: reimplement inotify using fsnotify
Just to close this out, the fix (for all architectures) is now upstream:
commit 9e572cc9877ee6c43af60778f6b8d5ba0692d935
Author: Eric Paris <eparis@redhat.com>
Date: Fri Jan 15 12:12:24 2010 -0500
inotify: do not reuse watch descriptors
James
prev parent reply other threads:[~2010-01-18 17:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20091220234610.GG11237@jade.home>
[not found] ` <1261354364.25157.246.camel@localhost>
[not found] ` <20091221003500.GK11237@jade.home>
[not found] ` <1261357334.25157.272.camel@localhost>
2010-01-03 23:23 ` Unexpected behaviour of idr_get_empty_slot() on parisc Ben Hutchings
2010-01-03 23:50 ` Kyle McMartin
2010-01-15 16:26 ` James Bottomley
2010-01-18 17:12 ` James Bottomley [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=1263834772.2773.63.camel@mulgrave.site \
--to=james.bottomley@hansenpartnership.com \
--cc=ben@decadent.org.uk \
--cc=kyle@mcmartin.ca \
--cc=linux-parisc@vger.kernel.org \
--cc=ryan@debian.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 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.