public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: The Peach <smartart@tiscali.it>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bug? VFAT copy problem
Date: Wed, 22 Nov 2006 16:30:01 +0100	[thread overview]
Message-ID: <20061122163001.0d291978@localhost> (raw)
In-Reply-To: <87mz6kajks.fsf@duaron.myhome.or.jp>

On Wed, 22 Nov 2006 00:46:43 +0900
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> wrote:

> Can you try the attached debug patch? 

Here is the debug for the copy of a normal file over vfat:

# cp -v DSCN5970\(1\).JPG /mnt/loop/
`DSCN5970(1).JPG' -> `/mnt/loop/DSCN5970(1).JPG'

and the output on dmesg:
vfat_hashi: parent d528a514, parent->d_op e0fbf5c0
vfat_hashi: parent /, name DSCN5970(1).JPG
vfat_lookup: name DSCN5970(1).JPG
vfat_hashi: parent d528a514, parent->d_op e0fbf5c0
vfat_hashi: parent /, name DSCN5970(1).JPG
vfat_cmpi: parent d528a514, parent->d_op e0fbf5c0
vfat_cmpi: a DSCN5970(1).JPG, b DSCN5970(1).JPG
vfat_revalidate: name DSCN5970(1).JPG, nd c9f1af30, flags 00000300             
vfat_lookup: name DSCN5970(1).JPG
vfat_create: name DSCN5970(1).JPG
vfat_add_entry: 0: DSCN59~1, JPG
vfat_add_entry: 1: DSCN5, 970(1), .J
vfat_add_entry: 2: PG
vfat_create: err 0

and the copy of an "abnormal" file:

# cp -v DSCN5980.JPG /mnt/loop/
`DSCN5980.JPG' -> `/mnt/loop/DSCN5980.JPG'

and its dmesg output:
vfat_hashi: parent d528a514, parent->d_op e0fbf5c0
vfat_hashi: parent /, name DSCN5980.JPG
vfat_cmpi: parent d528a514, parent->d_op e0fbf5c0
vfat_cmpi: a dscn5980.jpg, b DSCN5980.JPG
vfat_hashi: parent d528a514, parent->d_op e0fbf5c0
vfat_hashi: parent /, name DSCN5980.JPG
vfat_cmpi: parent d528a514, parent->d_op e0fbf5c0
vfat_cmpi: a dscn5980.jpg, b DSCN5980.JPG
vfat_create: name dscn5980.jpg
vfat_add_entry: 0: DSCN5980, JPG
vfat_add_entry: 1: dscn5, 980.jp, g
vfat_create: err 0

then:

# ls -l /mnt/loop/
totale 1363
-rwxr-xr-x 1 root root 695514 22 nov 16:21 DSCN5970(1).JPG
-rwxr-xr-x 1 root root 699770 22 nov 16:25 dscn5980.jpg

and its output:
vfat_hashi: parent d528a514, parent->d_op e0fbf5c0
vfat_hashi: parent /, name DSCN5970(1).JPG                                     
vfat_cmpi: parent d528a514, parent->d_op e0fbf5c0
vfat_cmpi: a DSCN5970(1).JPG, b DSCN5970(1).JPG
vfat_revalidate: name DSCN5970(1).JPG, nd c9f18ef8, flags 00000000
vfat_lookup: name DSCN5970(1).JPG
vfat_hashi: parent d528a514, parent->d_op e0fbf5c0
vfat_hashi: parent /, name dscn5980.jpg
vfat_cmpi: parent d528a514, parent->d_op e0fbf5c0
vfat_cmpi: a dscn5980.jpg, b dscn5980.jpg


> And if you comment-in the
> following parts, does this problem fix?

I will repatch asap and post the result.

-- 
Matteo 'Peach' Pescarin

ICQ UIN = 71110111
Jabber ID = smartart@unstable.nl
Web Site = http://www.smartart.it
GeCHI = http://www.gechi.it

  parent reply	other threads:[~2006-11-22 15:30 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-20 15:42 bug? VFAT copy problem The Peach
2006-11-20 17:32 ` OGAWA Hirofumi
2006-11-20 17:49   ` The Peach
2006-11-21 15:46     ` OGAWA Hirofumi
2006-11-22 14:02       ` [OT] " Sergio Monteiro Basto
2006-11-22 14:53         ` DervishD
2006-11-22 16:07           ` OGAWA Hirofumi
2006-11-22 18:21             ` DervishD
2006-11-23  0:56           ` Sergio Monteiro Basto
2006-11-23  9:13             ` DervishD
2006-11-23 11:26               ` The Peach
2006-11-23 15:43                 ` DervishD
2006-11-23 11:38               ` OGAWA Hirofumi
2006-11-23 11:50                 ` [OT] " Renato S. Yamane
2006-11-23 11:59                   ` OGAWA Hirofumi
2006-11-23 19:21                     ` Sergio Monteiro Basto
2006-11-22 15:30       ` The Peach [this message]
2006-11-22 16:15         ` OGAWA Hirofumi
2006-11-22 19:10           ` The Peach
2006-11-22 19:29             ` OGAWA Hirofumi
2006-11-22 19:38               ` The Peach
2006-11-22 19:51                 ` OGAWA Hirofumi
2006-11-22 22:21                   ` The Peach
2006-11-23 11:32                     ` OGAWA Hirofumi
2006-11-23  3:50       ` junjiec
2006-11-23 11:08         ` OGAWA Hirofumi

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=20061122163001.0d291978@localhost \
    --to=smartart@tiscali.it \
    --cc=hirofumi@mail.parknet.co.jp \
    --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