From: roma1390 <roma1390@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, stable@kernel.org
Subject: Re: [stable] nfs kernel server causes: kernel BUG at include/linux/module.h:386!
Date: Mon, 10 May 2010 09:33:12 +0300 [thread overview]
Message-ID: <4BE7A8A8.40204@gmail.com> (raw)
In-Reply-To: <20100507165606.GA795@kroah.com>
Greg KH wrote:
> If you can't test it, if I add that commit id to .27, I don't see how
> that would help you out at all, right?
There isn't a big like to test on production. But rescent that same bug was
triggered on testing in virtual machine. So theoretically this is only matter
of human time resource.
There is hope that commit to 2.26.x will be taken by debian, and updated
kernel will be propagated by debian update system.
> Can you poke the debian developers about this?
Case are reported[1] to debian and waiting for any progress.
1. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=532561#21
prev parent reply other threads:[~2010-05-10 6:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 5:47 nfs kernel server causes: kernel BUG at include/linux/module.h:386! roma1390
2010-05-06 6:03 ` [stable] " Greg KH
2010-05-07 7:10 ` roma1390
2010-05-07 16:56 ` Greg KH
2010-05-10 6:33 ` roma1390 [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=4BE7A8A8.40204@gmail.com \
--to=roma1390@gmail.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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