From: Suresh Jayaraman <sjayaraman-IBi9RG/b67k@public.gmane.org>
To: Federico Sauter <fsauter-LVkJPw3T+odGBRGhe+f61g@public.gmane.org>
Cc: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Issue with upgrade to kernel 3.4.10 -> invalid argument error
Date: Wed, 17 Oct 2012 15:25:24 +0530 [thread overview]
Message-ID: <507E808C.1020401@suse.com> (raw)
In-Reply-To: <507D934E.9010304-LVkJPw3T+odGBRGhe+f61g@public.gmane.org>
On 10/16/2012 10:33 PM, Federico Sauter wrote:
> Greetings,
>
>
> I am having an issue mounting CIFS shares since we upgraded our Linux
> kernel from 2.6.27 to 3.4.10. Each time I try to mount a share drive I
> get an "Invalid argument" error message even though I am using the same
> command line that had previously worked, e.g.:
>
A quick look suggests that the symptom is similar to the one fixed by
the below commit
commit e73f843a3235a19de38359c91586e9eadef12238
Author: Suresh Jayaraman <sjayaraman-IBi9RG/b67k@public.gmane.org>
Date: Tue Jun 12 07:15:50 2012 +0530
cifs: fix parsing of password mount option
It might be worth trying to see whether the commit fixes the problem you
are seeing.
Thanks
Suresh
next prev parent reply other threads:[~2012-10-17 9:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 17:03 Issue with upgrade to kernel 3.4.10 -> invalid argument error Federico Sauter
[not found] ` <CAH2r5mvFzSy5+SxpiBvuLydrsQcuJZn=5s6VCKgWO+K0iergMQ@mail.gmail.com>
[not found] ` <CAH2r5mvFzSy5+SxpiBvuLydrsQcuJZn=5s6VCKgWO+K0iergMQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-10-16 19:04 ` Fwd: " Steve French
2012-10-17 13:42 ` Federico Sauter
[not found] ` <507D934E.9010304-LVkJPw3T+odGBRGhe+f61g@public.gmane.org>
2012-10-17 9:55 ` Suresh Jayaraman [this message]
[not found] ` <507E808C.1020401-IBi9RG/b67k@public.gmane.org>
2012-10-17 13:47 ` Federico Sauter
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=507E808C.1020401@suse.com \
--to=sjayaraman-ibi9rg/b67k@public.gmane.org \
--cc=fsauter-LVkJPw3T+odGBRGhe+f61g@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox