From: "J. Bruce Fields" <bfields@fieldses.org>
To: Bodo Stroesser <bstroesser@ts.fujitsu.com>
Cc: neilb@suse.de, linux-nfs@vger.kernel.org
Subject: Re: sunrpc/cache.c: races while updating cache entries
Date: Fri, 5 Apr 2013 08:40:25 -0400 [thread overview]
Message-ID: <20130405124025.GC951@fieldses.org> (raw)
In-Reply-To: <61eb00$3itd78@dgate20u.abg.fsc.net>
On Thu, Apr 04, 2013 at 07:59:35PM +0200, Bodo Stroesser wrote:
> There is no reason for apologies. The thread meanwhile seems to be a bit
> confusing :-)
>
> Current state is:
>
> - Neil Brown has created two series of patches. One for SLES11-SP1 and a
> second one for -SP2
>
> - AFAICS, the series for -SP2 will match with mainline also.
>
> - Today I found and fixed the (hopefully) last problem in the -SP1 series.
> My test using this patchset will run until Monday.
>
> - Provided the test on SP1 succeeds, probably on Tuesday I'll start to test
> the patches for SP2 (and mainline). If it runs fine, we'll have a tested
> patchset not later than Mon 15th.
OK, great, as long as it hasn't just been forgotten!
I'd also be curious to understand why we aren't getting a lot of
complaints about this from elsewhere.... Is there something unique
about your setup? Do the bugs that remain upstream take a long time to
reproduce?
--b.
next parent reply other threads:[~2013-04-05 12:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <61eb00$3itd78@dgate20u.abg.fsc.net>
2013-04-05 12:40 ` J. Bruce Fields [this message]
[not found] <61eb00$3oamkh@dgate20u.abg.fsc.net>
2013-06-13 1:54 ` sunrpc/cache.c: races while updating cache entries NeilBrown
2013-06-13 2:04 ` J. Bruce Fields
2013-06-03 14:27 Bodo Stroesser
-- strict thread matches above, loose matches on Subject: below --
2013-04-19 16:55 Bodo Stroesser
2013-05-10 7:51 ` Namjae Jeon
2013-05-13 4:08 ` Namjae Jeon
[not found] <d6437a$47jkcm@dgate10u.abg.fsc.net>
2013-04-05 21:08 ` J. Bruce Fields
2013-04-05 15:33 Bodo Stroesser
2013-04-04 17:59 Bodo Stroesser
[not found] <61eb00$3hon1j@dgate20u.abg.fsc.net>
2013-04-03 18:36 ` J. Bruce Fields
2013-03-21 16:41 Bodo Stroesser
[not found] <61eb00$3hl8ah@dgate20u.abg.fsc.net>
2013-03-20 23:33 ` NeilBrown
2013-03-20 18:45 Bodo Stroesser
[not found] <d6437a$45t6bs@dgate10u.abg.fsc.net>
2013-03-20 4:39 ` NeilBrown
2013-03-19 19:58 Bodo Stroesser
[not found] <d6437a$45efvo@dgate10u.abg.fsc.net>
2013-03-19 3:23 ` NeilBrown
2013-03-15 20:35 Bodo Stroesser
2013-03-14 17:31 Bodo Stroesser
2013-03-13 16:47 Bodo Stroesser
[not found] <61eb00$3gpm51@dgate20u.abg.fsc.net>
2013-03-13 5:55 ` NeilBrown
2013-03-11 16:13 Bodo Stroesser
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=20130405124025.GC951@fieldses.org \
--to=bfields@fieldses.org \
--cc=bstroesser@ts.fujitsu.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).