public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Elladan <elladan@eskimo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Consistent deadlock+crash in 2.6.5 when writing large file to CFSd (over NFS)
Date: Thu, 20 May 2004 21:27:52 +0200	[thread overview]
Message-ID: <20040520192751.GD5215@openzaurus.ucw.cz> (raw)
In-Reply-To: <20040519075336.GA2020@eskimo.com>

Hi!

> I'm getting consistent crashes in 2.6.5 when I write a large file to cfs
> (crypto file system).  This is a user daemon that implements an NFS
> export of encrypted files on disk.
> 
> Basically, what appears to happen is that it's deadlocking something in
> the IO system.  I can't really tell what, because the entire system
> seizes up soon afterward.

...

> Any ideas?

Are you doing r/w mount from process that is on local machine?
That would be broken by design.
				Pavel
-- 
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms         


      reply	other threads:[~2004-05-22 17:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-19  7:53 Consistent deadlock+crash in 2.6.5 when writing large file to CFSd (over NFS) Elladan
2004-05-20 19:27 ` Pavel Machek [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=20040520192751.GD5215@openzaurus.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=elladan@eskimo.com \
    --cc=linux-kernel@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