All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sachin Prabhu <sprabhu-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: chris2553-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org
Cc: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: 3.4.0-rc2+ - CIFS mount failure
Date: Tue, 10 Apr 2012 10:39:32 +0100	[thread overview]
Message-ID: <1334050772.2149.4.camel@localhost> (raw)
In-Reply-To: <201204100823.24207.chris2553-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>

On Tue, 2012-04-10 at 08:23 +0100, Chris Clayton wrote:
> HI,
> 
> I'm testing the latest and greatest from Linus' tree and can't mount partitions 
> on a nas server. The mounts work fine with 3.3.1. For the failing kernel, git 
> describe gives v3.4-rc2-2-g258f742.
> 
> What I see is:
> 
> [chris:~]$ sudo mount /media/nas/share
> mount error(22): Invalid argument
> Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
> 
> Dmesg shows the message:
> 
> CIFS: Unknown mount option "user="
> 
> The related entry in /etc/fstab is:
> 
> //nas/Share /media/nas/share cifs 
> rw,noauto,nosuid,nodev,user,guest,uid=1000,gid=100,file_mode=0666  0 0
> 
> Let me know how I can help fix this regression.
> 
> Please cc me - I'm not subscribed.
> 
> Thanks
> 
> Chris


Chris,

This was caused due to a regression introduced by the patch with commit
8830d7e07a5e38bc47650a7554b7c1cfd49902bf
which cleaned up the mount options parser.

The patch doesn't handle blank user= mount option passed as a mount
option. The patch is trivial and requires similar handling as the blank
password option.
http://article.gmane.org/gmane.linux.kernel.cifs/5762

Sachin Prabhu

  parent reply	other threads:[~2012-04-10  9:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-10  7:23 3.4.0-rc2+ - CIFS mount failure Chris Clayton
     [not found] ` <201204100823.24207.chris2553-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2012-04-10  9:39   ` Sachin Prabhu [this message]
2012-04-10 11:16     ` Jeff Layton
     [not found]       ` <20120410071630.567d70cb-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2012-04-10 13:13         ` Chris Clayton
     [not found]           ` <201204101413.27748.chris2553-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
2012-04-10 13:28             ` Sachin Prabhu
2012-04-10 17:12               ` [PATCH] Cleanup handling of NULL value passed for a mount option Sachin Prabhu
2012-04-10 17:17                 ` Jeff Layton
2012-04-10 22:00                 ` Chris Clayton
2012-04-11  2:17                 ` Steve French
     [not found]                   ` <CAH2r5mtrYxLueLL9VDSWE2G+86ZDyqXaFdOJz0FkNp8J0OzEUQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-04-11 12:03                     ` Sachin Prabhu

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=1334050772.2149.4.camel@localhost \
    --to=sprabhu-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=chris2553-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.