Re: 2.6.24-rc4: mount.ntfs-3g hangs when smack is enabled

[Casey Schaufler]

--- "Luiz Fernando N. Capitulino" <lcapitulino@xxxxxxxxxxxxxxx> wrote:

> 
>  Hi Casey,
> 
>  I'm not sure whether this is a smack problem, but Mandriva users are
> reporting that mount.ntfs-3g (ntfs driver, uses FUSE) hangs when
> they try to mount their NTFS partition.
> 
>  I could reproduce the problem with a vanilla 2.6.24-rc4 kernel, and it
> only happens when Smack is enabled.

Thank you for the report. I will look into it. 

>  Besides that, I've been told that a similar problem happens with unionfs,
> but I haven't tried to reproduce it yet.
> 
>  What follows is the output of SysRq+D:
> 
> """
> Showing all locks held in the system:
> 1 lock held by mingetty/4193:
>  #0:  (&tty->atomic_read_lock){--..}, at: [<c0229650>] read_chan+0x1e5/0x605
> 1 lock held by mingetty/4194:
>  #0:  (&tty->atomic_read_lock){--..}, at: [<c0229650>] read_chan+0x1e5/0x605
> 1 lock held by mingetty/4195:
>  #0:  (&tty->atomic_read_lock){--..}, at: [<c0229650>] read_chan+0x1e5/0x605
> 1 lock held by mingetty/4196:
>  #0:  (&tty->atomic_read_lock){--..}, at: [<c0229650>] read_chan+0x1e5/0x605
> 1 lock held by mingetty/4197:
>  #0:  (&tty->atomic_read_lock){--..}, at: [<c0229650>] read_chan+0x1e5/0x605
> 2 locks held by mount.ntfs-3g/4667:
>  #0:  (&type->s_umount_key#19){--..}, at: [<c01726f0>] sget+0x202/0x350
>  #1:  (&isp->smk_lock){--..}, at: [<c01c7f87>] smack_d_instantiate+0x39/0x129
> 1 lock held by bash/4844:
>  #0:  (&tty->atomic_read_lock){--..}, at: [<c0229650>] read_chan+0x1e5/0x605
> 1 lock held by bash/5389:
>  #0:  (&tty->atomic_read_lock){--..}, at: [<c0229650>] read_chan+0x1e5/0x605
> 1 lock held by bash/5498:
>  #0:  (&tty->atomic_read_lock){--..}, at: [<c0229650>] read_chan+0x1e5/0x605
> """
> 
>  Let me know if you need more information.
> 
>  Best regards.
> 
> -- 
> Luiz Fernando N. Capitulino
> 
> 


Casey Schaufler
casey@xxxxxxxxxxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/