Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #59111 > unrolled thread

Bug#877764: linux-image-amd64: cifs mount gets automatically the file_mode=0755,dir_mode=0755 options

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#877764: linux-image-amd64: cifs mount gets automatically the file_mode=0755,dir_mode=0755 options matecs <matecs@niif.hu> - 2017-10-05 11:00 +0200
    Bug#877764: linux-image-amd64: cifs mount gets automatically the file_mode=0755,dir_mode=0755 options Ben Hutchings <ben@decadent.org.uk> - 2017-10-05 18:50 +0200
      Bug#877764: linux-image-amd64: cifs mount gets automatically the file_mode=0755,dir_mode=0755 options matecs <matecs@niif.hu> - 2017-10-05 19:20 +0200
        Bug#877764: linux-image-amd64: cifs mount gets automatically the file_mode=0755,dir_mode=0755 options matecs <matecs@niif.hu> - 2017-10-06 10:10 +0200
    Processed: Re: Bug#877764: linux-image-amd64: cifs mount gets  automatically the file_mode=0755,dir_mode=0755 options owner@bugs.debian.org (Debian Bug Tracking System) - 2017-10-05 18:50 +0200

#59111 — Bug#877764: linux-image-amd64: cifs mount gets automatically the file_mode=0755,dir_mode=0755 options

Package: linux-image-amd64
Version: 4.13+86
Severity: normal

Dear Maintainer,

i'm mounting my shares through cifs for years.
when sid pulled the 4.13 kernel, i noticed that these mounts
automatically get the file_mode=0755 and dir_mode=0755 options.

the fstab looks like this:
//nas.mchome.nop.hu/mc36     /nfs   cifs 
user=mc36,password=***,uid=mc36,gid=mc36   0   0

then the resulting mount looks like this:
//nas.mchome.nop.hu/mc36 on /nfs type cifs 
(rw,relatime,vers=3.0,cache=strict,username=mc36,domain=,uid=1000,forceuid,gid=1000,forcegid,addr=2001:0db8:1001:0255:0200:4eff:fe36:4e35,file_mode=0755,dir_mode=0755,nounix,serverino,mapposix,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1,user=mc36)

things look similarly if i add vers=2.0 to the fstab. only vers=1.0 
solves the issue.


-- System Information:
Debian Release: buster/sid
   APT prefers unstable
   APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=locale: Cannot set LC_CTYPE 
to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
ANSI_X3.4-1968), LANGUAGE=en_US (charmap=locale: Cannot set LC_CTYPE to 
default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-image-amd64 depends on:
ii  linux-image-4.13.0-1-amd64  4.13.4-1

linux-image-amd64 recommends no packages.

linux-image-amd64 suggests no packages.

-- debconf information:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
	LANGUAGE = (unset),
	LC_ALL = (unset),
	LANG = "en_US"
     are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory

[toc] | [next] | [standalone]

#59115

[Multipart message — attachments visible in raw view] — view raw

Control: reassign -1 src:linux 4.13.4-1
Control: tag -1 moreinfo

On Thu, 2017-10-05 at 10:18 +0200, matecs wrote:
> Package: linux-image-amd64
> Version: 4.13+86
> Severity: normal
> 
> Dear Maintainer,
> 
> i'm mounting my shares through cifs for years.
> when sid pulled the 4.13 kernel, i noticed that these mounts
> automatically get the file_mode=0755 and dir_mode=0755 options.

It appears that this indicates the server does not support Unix
extensions.

What is the file server running?

> the fstab looks like this:
> //nas.mchome.nop.hu/mc36     /nfs   cifs 
> user=mc36,password=***,uid=mc36,gid=mc36   0   0
> 
> then the resulting mount looks like this:
> //nas.mchome.nop.hu/mc36 on /nfs type cifs 
> (rw,relatime,vers=3.0,cache=strict,username=mc36,domain=,uid=1000,for
> ceuid,gid=1000,forcegid,addr=2001:0db8:1001:0255:0200:4eff:fe36:4e35,
> file_mode=0755,dir_mode=0755,nounix,serverino,mapposix,rsize=1048576,
> wsize=1048576,echo_interval=60,actimeo=1,user=mc36)

And the 'nounix' confirms that.

Are there any messages in the kernel log relating to cifs?

> things look similarly if i add vers=2.0 to the fstab. only vers=1.0 
> solves the issue.
[...]

Version 1 should no longer be used as it has well-known and unfixable
security issues.  The default protocol version for the cifs filesystem
was changed to 3 in Linux 4.13:
https://git.kernel.org/linus/eef914a9eb5eb83e60eb498315a491cd1edc13a1

Ben.

-- 
Ben Hutchings
Make three consecutive correct guesses and you will be considered an
expert.

[toc] | [prev] | [next] | [standalone]

#59117

hi,

>> when sid pulled the 4.13 kernel, i noticed that these mounts
>> automatically get the file_mode=0755 and dir_mode=0755 options.
> 
> It appears that this indicates the server does not support Unix
> extensions.
> 
> What is the file server running?
it's the debian sid's samba daemon: Version 4.6.7-Debian

> And the 'nounix' confirms that.
ohhh, i did not noticed this. anyway i've looked at smbd config
and i contains the line unix extensions = yes.

> 
> Are there any messages in the kernel log relating to cifs?
nothing interesting.
[   15.659306] FS-Cache: Netfs 'cifs' registered for caching
[   15.659358] Key type cifs.spnego registered
[   15.659362] Key type cifs.idmap registered

regards,
cs

[toc] | [prev] | [next] | [standalone]

#59129

[Multipart message — attachments visible in raw view] — view raw

On 10/05/2017 07:03 PM, matecs wrote:
>> And the 'nounix' confirms that.
> ohhh, i did not noticed this. anyway i've looked at smbd config
> and i contains the line unix extensions = yes.
diggde a bit around but found nothing useful about this topic.
so finally i've done two captures, one with vers=1.0 and one with vers=3.0.
seemingly this bit is not defined in the smb3 header, or i did not
found it. anyway with smb1, my server offers the capability, and
i've used the same configuration for both captures.
regards,
cs

[toc] | [prev] | [next] | [standalone]

#59116 — Processed: Re: Bug#877764: linux-image-amd64: cifs mount gets automatically the file_mode=0755,dir_mode=0755 options

Processing control commands:

> reassign -1 src:linux 4.13.4-1
Bug #877764 [linux-image-amd64] linux-image-amd64: cifs mount gets automatically the file_mode=0755,dir_mode=0755 options
Bug reassigned from package 'linux-image-amd64' to 'src:linux'.
No longer marked as found in versions linux-latest/86.
Ignoring request to alter fixed versions of bug #877764 to the same values previously set
Bug #877764 [src:linux] linux-image-amd64: cifs mount gets automatically the file_mode=0755,dir_mode=0755 options
Marked as found in versions linux/4.13.4-1.
> tag -1 moreinfo
Bug #877764 [src:linux] linux-image-amd64: cifs mount gets automatically the file_mode=0755,dir_mode=0755 options
Added tag(s) moreinfo.

-- 
877764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877764
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web