From: "J. Bruce Fields" <bfields@fieldses.org>
To: Frank van Maarseveen <frankvm@frankvm.com>
Cc: Linux NFS mailing list <linux-nfs@vger.kernel.org>,
netdev@vger.kernel.org
Subject: Re: assertion (!sk->sk_forward_alloc) failed at net/ipv4/af_inet.c (157)
Date: Thu, 14 Aug 2008 15:29:20 -0400 [thread overview]
Message-ID: <20080814192920.GG23859@fieldses.org> (raw)
In-Reply-To: <20080814152421.GA8056@janus>
On Thu, Aug 14, 2008 at 05:24:21PM +0200, Frank van Maarseveen wrote:
> There are not many reports of this but it seems related to stopping the
> NFS server. I'm seeing them occasionally on system shutdown right after
>
> nfsd: last server has exited
> nfsd: unexporting all filesystems
>
> kernels: 2.6.25, 2.6.26
A couple minutes with grep wasn't enough for me to figure out what
sk_forward_alloc was or why this assertion should be failing, so I'm
cc'ing netdev in hopes they might have some hints!
--b.
next prev parent reply other threads:[~2008-08-14 19:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-14 15:24 assertion (!sk->sk_forward_alloc) failed at net/ipv4/af_inet.c (157) Frank van Maarseveen
2008-08-14 19:29 ` J. Bruce Fields [this message]
2008-11-03 13:01 ` Frank van Maarseveen
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=20080814192920.GG23859@fieldses.org \
--to=bfields@fieldses.org \
--cc=frankvm@frankvm.com \
--cc=linux-nfs@vger.kernel.org \
--cc=netdev@vger.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