From: Leszek Urbanski <tgr.kb@moo.pl>
To: linux-nfs@vger.kernel.org
Subject: Deadlock/crash in 2.6.32.12 when copying large files
Date: Wed, 26 May 2010 00:26:57 +0200 [thread overview]
Message-ID: <20100525222657.GA14891@moo.pl> (raw)
Hi,
I've hit https://bugzilla.kernel.org/show_bug.cgi?id=15578 again with
2.6.32.12 on amd64.
I can reproduce it every time when copying large (>2G) files over NFS.
The call trace is at https://bugzilla.kernel.org/attachment.cgi?id=26519
Needless to say it results in a system crash (kswapd deadlock, network stack
failure because of memory allocation failure for SKBs, etc.).
Trond Myklebust closed this bug a while ago, but apparently it's not completely
fixed and needs to be re-opened.
--
Leszek Urbanski
next reply other threads:[~2010-05-25 22:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-25 22:26 Leszek Urbanski [this message]
2010-05-25 22:43 ` Deadlock/crash in 2.6.32.12 when copying large files Lukas Hejtmanek
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=20100525222657.GA14891@moo.pl \
--to=tgr.kb@moo.pl \
--cc=linux-nfs@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;
as well as URLs for NNTP newsgroup(s).