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]
Date:	Sat, 7 Jul 2007 23:38:45 +0530
From:	"Satyam Sharma" <satyam.sharma@...il.com>
To:	"Albert Cahalan" <acahalan@...il.com>
Cc:	linux-kernel@...r.kernel.org, linux-cifs-client@...ts.samba.org
Subject: Re: partially mounted cifs filesystem

Hi Albert,

[ added linux-cifs-client to Cc: ]

On 7/7/07, Albert Cahalan <acahalan@...il.com> wrote:
> I had one share mounted, from XP to Linux, and wanted another.
> At first I had an incorrect setting on the XP box, almost
> certainly related to permissions. The mount failed of course.
> Running "mount" showed that the filesystem was not mounted,
> but apparently it didn't remain fully unmounted either.
> There was also nothing under the mount point, and the "ls -l"
> data (directory size and link count) looked like ext3.

That means nothing was mounted there ...

> I changed settings on the XP box numerous times. After many
> frustrating attempts, I ran "umount" on the mount point and
> then successfully mounted the filesystem.

... but still umount succeeded? Didn't it complain about nothing
being mounted there in the first place? Surprising that it actually
resolved the problem ...

> I'll guess that the kernel returned an error for my early
> attempts at mounting, but left open a CIFS connection.
>
> I suppose the cifs error handling is buggy.

Yes, that could be the case. Could you please:

1. Tell us which kernel version was it? .config?
2. Was there some dmesg output from the failed mount(2) attempt?
3. What was the mount command line / options?

Then:

1. Rebuild kernel with CIFS_DEBUG2.
2. Revert back (on the XP share export side) to the buggy / incorrect
settings -- so that you can try and reproduce the problem.
3. Let us know if you could reproduce, if so, any debug ouput / etc?

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ