All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-ntfs-dev@lists.sourceforge.net
Subject: Re: [Linux-NTFS-Dev] 2.6.23 regression: second access of empty ntfs file leads to D	state hang
Date: Mon, 29 Oct 2007 12:45:11 +0100	[thread overview]
Message-ID: <1193658311.7324.2.camel@Homer.simpson.net> (raw)
In-Reply-To: <E3E758D0-25AC-45B8-9BAB-F8CDF75AF3CA@cam.ac.uk>

[-- Attachment #1: Type: text/plain, Size: 437 bytes --]

On Mon, 2007-10-29 at 10:31 +0000, Anton Altaparmakov wrote:

> Could you post the complete dmesg output, please?

Attached.  This is after a reboot though, but a fresh attempt to sum the
0 length file, so the NTFS message is there.

> Nothing related has changed in the NTFS driver between 2.6.22.10 and  
> 2.6.23 so I expect something else to be at fault here.
> 
> Could you post your .config as well, please?

Also attached.

-Mike

[-- Attachment #2: dmesg.gz --]
[-- Type: application/x-gzip, Size: 9244 bytes --]

[-- Attachment #3: config.gz --]
[-- Type: application/x-gzip, Size: 12875 bytes --]

  reply	other threads:[~2007-10-29 11:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-29  6:08 2.6.23 regression: second access of empty ntfs file leads to D state hang Mike Galbraith
2007-10-29  6:18 ` Mike Galbraith
2007-10-29 10:40   ` Anton Altaparmakov
2007-10-29 10:31 ` [Linux-NTFS-Dev] " Anton Altaparmakov
2007-10-29 11:45   ` Mike Galbraith [this message]
2007-10-29 13:39     ` Anton Altaparmakov
2007-10-29 13:41       ` Anton Altaparmakov
2007-10-29 14:43       ` Mike Galbraith
2007-10-29 15:18         ` Mike Galbraith
2007-10-30  8:00           ` Mike Galbraith
2007-10-30  9:23             ` Anton Altaparmakov
2007-11-02 19:22               ` Anton Altaparmakov
2007-11-03  4:56                 ` Mike Galbraith
2007-11-03  7:27                   ` Anton Altaparmakov

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=1193658311.7324.2.camel@Homer.simpson.net \
    --to=efault@gmx.de \
    --cc=aia21@cam.ac.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-ntfs-dev@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.