From: Shyam Kaushik <shyam@zadarastorage.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Tejun Heo <tj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: RE: BUG REPORT - IDR wraps around at 30-bits - works very bad with NFSD/SCTP
Date: Tue, 13 Aug 2013 13:21:12 +0530 [thread overview]
Message-ID: <446f41f4a3ea0c758b05c0348d2b6f5d@mail.gmail.com> (raw)
In-Reply-To: <20130813072616.GA14019@kroah.com>
It was just more time from me on this:-) But anyways since you wanted I
tried.
I tested 3.10.6-031006-generic & it works perfect in there!
[ 832.513688] Processing for min_stateid[0]
[ 832.513701] Allocated new_stid[0]
[ 832.513703] Dumping entries in IDR
[ 832.513705] IDR Actual ID[0] == Expected Value[0]
[ 832.513710]
[ 832.513710] Processing for min_stateid[1073741823]
[ 832.513713] Allocated new_stid[1073741823]
[ 832.513714] Dumping entries in IDR
[ 832.513729] IDR Actual ID[1073741823] == Expected Value[1073741823]
[ 832.513731]
[ 832.513731] Processing for min_stateid[1073741824]
[ 832.513736] Allocated new_stid[1073741824]
[ 832.513737] Dumping entries in IDR
[ 832.513739] IDR Actual ID[1073741824] == Expected Value[1073741824]
[ 832.513754]
[ 832.513754] Processing for min_stateid[2147483647]
[ 832.513763] Allocated new_stid[2147483647]
[ 832.513765] Dumping entries in IDR
[ 832.513779] IDR Actual ID[2147483647] == Expected Value[2147483647]
Any chances of backporting some parts of fix to <3.9 kernels?
Thanks.
--Shyam
-----Original Message-----
From: Greg KH [mailto:gregkh@linuxfoundation.org]
Sent: Tuesday, August 13, 2013 12:56 PM
To: Shyam Kaushik
Cc: Tejun Heo; Andrew Morton; linux-kernel@vger.kernel.org
Subject: Re: BUG REPORT - IDR wraps around at 30-bits - works very bad
with NFSD/SCTP
On Tue, Aug 13, 2013 at 12:51:14PM +0530, Shyam Kaushik wrote:
> Hi Greg,
>
> Unfortunately we don't have a 3.9/3.10 environment here. So if IDR
> developers can try the example code, it should show if the bug is still
> present in there. Thanks.
There shouldn't be anything in 3.10 preventing you from building and
testing it out, is there? Or do you have something that restricts you
to specific kernel versions?
thanks,
greg k-h
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2013.0.2904 / Virus Database: 3211/6571 - Release Date: 08/12/13
next prev parent reply other threads:[~2013-08-13 7:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 7:01 BUG REPORT - IDR wraps around at 30-bits - works very bad with NFSD/SCTP Shyam Kaushik
2013-08-13 7:19 ` Greg KH
2013-08-13 7:21 ` Shyam Kaushik
2013-08-13 7:26 ` Greg KH
2013-08-13 7:51 ` Shyam Kaushik [this message]
2013-08-13 14:51 ` Tejun Heo
2013-08-13 7:33 ` Greg KH
2013-08-13 7:34 ` Shyam Kaushik
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=446f41f4a3ea0c758b05c0348d2b6f5d@mail.gmail.com \
--to=shyam@zadarastorage.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox