linux-kernel - Re: BISECTED REGRESSION: 2.6.26-rc2: FUSE changes break mount of ntfs-3g

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <df47b87a0805191117m278580d2n2e23c48452ee4a19@mail.gmail.com>
Date:	Mon, 19 May 2008 21:17:19 +0300
From:	"Ioan Ionita" <opslynx@...il.com>
To:	"Miklos Szeredi" <miklos@...redi.hu>
Cc:	linux-kernel@...r.kernel.org, mszeredi@...e.cz,
	a.p.zijlstra@...llo.nl, akpm@...ux-foundation.org
Subject: Re: BISECTED REGRESSION: 2.6.26-rc2: FUSE changes break mount of ntfs-3g

On Mon, May 19, 2008 at 10:14 AM, Miklos Szeredi <miklos@...redi.hu> wrote:

> Thanks.  I've tried to reproduce this bug, but was unable to.
>
> That patch looks OK to me, however there's something very weird going
> on if sysfs_add_one() gets called with an already existing name.
>
> Could you please post the full dmesg output?  That should include a
> line like
>
>  sysfs: duplicate filename 'foobar' can not be created
>
> What are the exact commands that you perform (or contents of
> /etc/fstab, etc. that might be relevant) to tirgger this bug?
>

I think you were unable to reproduce it because i just figured out
that it only occurs on a raid-0 partition managed by dmraid.
Ex:

Mounting the non-raid:
/dev/sdb3           10913       18242    58878225    7  HPFS/NTFS
root@...-desktop:~# mount /dev/sdb3 /next
root@...-desktop:~#

The raid-0:
/dev/mapper/isw_fjcgajage_raid3            4346       29841
204796620    7  HPFS/NTFS
root@...-desktop:~# mount /dev/mapper/isw_fjcgajage_raid3 /new
fuse: mount failed: Cannot allocate memory

NOTE that I've tried mounting other raid-0 NTFS partitions. Same
failure occurred. So it doesn't seem to be isolated to one partition.
RAID is the only common thing.

I've attached the full dmesg. Hope it helps.

View attachment "dmesg.txt" of type "text/plain" (31265 bytes)