From: Jesper Krogh <jesper-Q2TZfHgGEy4@public.gmane.org>
To: "J. Bruce Fields"
<public-bfields-uC3wQj2KruNg9hUCZPvPmw-wOFGN7rlS/M9smdsby/KFg@public.gmane.org>
Cc: Nikola Ciprich
<public-extmaillist-Jp3n8lUXroTtwjQa/ONI9g-wOFGN7rlS/M9smdsby/KFg@public.gmane.org>,
Harry Edmon
<public-harry-qmPYOCrcNLLyFCzt5hm0YvZ8FUJU4vz8-wOFGN7rlS/M9smdsby/KFg@public.gmane.org>,
Andrew Morton
<public-akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b-wOFGN7rlS/M9smdsby/KFg@public.gmane.org>,
public-linux-kernel-u79uwXL29TY76Z2rM5mHXA-wOFGN7rlS/M9smdsby/KFg@public.gmane.org,
public-linux-nfs-u79uwXL29TY76Z2rM5mHXA-wOFGN7rlS/M9smdsby/KFg@public.gmane.org,
public-nikola.ciprich-Jp3n8lUXroTtwjQa/ONI9g-wOFGN7rlS/M9smdsby/KFg@public.gmane.org
Subject: Re: 2.6.32.2 - WARNING: at lib/kref.c:43 kref_get+0x,23/0x2b()
Date: Wed, 24 Feb 2010 08:19:06 +0100 [thread overview]
Message-ID: <4B84D2EA.4090209@krogh.cc> (raw)
In-Reply-To: <20100220235105.GB15015@fieldses.org>
J. Bruce Fields wrote:
> On Wed, Feb 17, 2010 at 04:14:35PM +0100, Nikola Ciprich wrote:
>> Well,
>> I did a lot of stress tests, and it seems to be pretty random, and what's
>> worse, I think it is more then one problem, oh great...
>> Seems that at least one of my NFS problems was in fact caused by ext4 regression
>> (what FS are you using?)
>> applying this one: http://bugzilla.kernel.org/attachment.cgi?id=24975
>> improved things for me a lot (see http://bugzilla.kernel.org/show_bug.cgi?id=15231 for
>> full discussion).
>> I'll watch the machine for next few days and report...
>
> Is there *any* kernel (however old) on which you are confident you can
> *not* reproduce the kref bug?
I have got a bug that looks a lot like this on 2.6.32.8 yesterday less
than 24 hours after booting the first 2.6.32 kernel but we have been
running on 2.6.31 for 3 months before, so I'm fairly confident that it
is a .31 -> .32 regression.
http://lkml.org/lkml/2010/2/23/70
Jesper
--
Jesper
WARNING: multiple messages have this Message-ID (diff)
From: Jesper Krogh <jesper@krogh.cc>
To: "J. Bruce Fields"
<public-bfields-uC3wQj2KruNg9hUCZPvPmw@plane.gmane.org>
Cc: Nikola Ciprich
<public-extmaillist-Jp3n8lUXroTtwjQa/ONI9g@plane.gmane.org>,
Harry Edmon
<public-harry-qmPYOCrcNLLyFCzt5hm0YvZ8FUJU4vz8@plane.gmane.org>,
Andrew Morton
<public-akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@plane.gmane.org>,
public-linux-kernel-u79uwXL29TY76Z2rM5mHXA@plane.gmane.org,
public-linux-nfs-u79uwXL29TY76Z2rM5mHXA@plane.gmane.org,
public-nikola.ciprich-Jp3n8lUXroTtwjQa/ONI9g@plane.gmane.org
Subject: Re: 2.6.32.2 - WARNING: at lib/kref.c:43 kref_get+0x,23/0x2b()
Date: Wed, 24 Feb 2010 08:19:06 +0100 [thread overview]
Message-ID: <4B84D2EA.4090209@krogh.cc> (raw)
In-Reply-To: <20100220235105.GB15015@fieldses.org>
J. Bruce Fields wrote:
> On Wed, Feb 17, 2010 at 04:14:35PM +0100, Nikola Ciprich wrote:
>> Well,
>> I did a lot of stress tests, and it seems to be pretty random, and what's
>> worse, I think it is more then one problem, oh great...
>> Seems that at least one of my NFS problems was in fact caused by ext4 regression
>> (what FS are you using?)
>> applying this one: http://bugzilla.kernel.org/attachment.cgi?id=24975
>> improved things for me a lot (see http://bugzilla.kernel.org/show_bug.cgi?id=15231 for
>> full discussion).
>> I'll watch the machine for next few days and report...
>
> Is there *any* kernel (however old) on which you are confident you can
> *not* reproduce the kref bug?
I have got a bug that looks a lot like this on 2.6.32.8 yesterday less
than 24 hours after booting the first 2.6.32 kernel but we have been
running on 2.6.31 for 3 months before, so I'm fairly confident that it
is a .31 -> .32 regression.
http://lkml.org/lkml/2010/2/23/70
Jesper
--
Jesper
next prev parent reply other threads:[~2010-02-24 8:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 17:53 2.6.32.2 - WARNING: at lib/kref.c:43 kref_get+0x,23/0x2b() Harry Edmon
[not found] ` <4B4F5A00.4060604-qmPYOCrcNLLyFCzt5hm0YvZ8FUJU4vz8@public.gmane.org>
2010-01-22 23:03 ` Andrew Morton
2010-01-22 23:03 ` Andrew Morton
2010-01-27 19:05 ` J. Bruce Fields
2010-01-27 19:05 ` J. Bruce Fields
2010-01-27 23:01 ` Harry Edmon
2010-02-02 16:22 ` J. Bruce Fields
2010-02-16 18:22 ` Nikola Ciprich
2010-02-16 18:22 ` Nikola Ciprich
[not found] ` <20100216182248.GA4922-YtsXe8XL0VS8z6Q06MQEFCF40CQGThNF@public.gmane.org>
2010-02-16 20:21 ` J. Bruce Fields
2010-02-16 20:21 ` J. Bruce Fields
2010-02-16 20:27 ` Nikola Ciprich
[not found] ` <20100216202720.GB4922-YtsXe8XL0VS8z6Q06MQEFCF40CQGThNF@public.gmane.org>
2010-02-16 20:29 ` J. Bruce Fields
2010-02-16 20:29 ` J. Bruce Fields
2010-02-17 15:14 ` Nikola Ciprich
2010-02-17 15:14 ` Nikola Ciprich
[not found] ` <20100217151435.GC30897-K8br+RTdgN68z6Q06MQEFCF40CQGThNF@public.gmane.org>
2010-02-20 23:51 ` J. Bruce Fields
2010-02-20 23:51 ` J. Bruce Fields
2010-02-22 5:37 ` Nikola Ciprich
2010-02-24 7:19 ` Jesper Krogh [this message]
2010-02-24 7:19 ` Jesper Krogh
2010-02-23 9:17 ` Jesper Krogh
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=4B84D2EA.4090209@krogh.cc \
--to=jesper-q2tzfhggey4@public.gmane.org \
--cc=public-akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b-wOFGN7rlS/M9smdsby/KFg@public.gmane.org \
--cc=public-bfields-uC3wQj2KruNg9hUCZPvPmw-wOFGN7rlS/M9smdsby/KFg@public.gmane.org \
--cc=public-extmaillist-Jp3n8lUXroTtwjQa/ONI9g-wOFGN7rlS/M9smdsby/KFg@public.gmane.org \
--cc=public-harry-qmPYOCrcNLLyFCzt5hm0YvZ8FUJU4vz8-wOFGN7rlS/M9smdsby/KFg@public.gmane.org \
--cc=public-linux-kernel-u79uwXL29TY76Z2rM5mHXA-wOFGN7rlS/M9smdsby/KFg@public.gmane.org \
--cc=public-linux-nfs-u79uwXL29TY76Z2rM5mHXA-wOFGN7rlS/M9smdsby/KFg@public.gmane.org \
--cc=public-nikola.ciprich-Jp3n8lUXroTtwjQa/ONI9g-wOFGN7rlS/M9smdsby/KFg@public.gmane.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.