public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arthur Marsh <arthur.marsh@internode.on.net>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Serge Hallyn <serge.hallyn@canonical.com>,
	Kees Cook <keescook@google.com>,
	linux-cifs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: fs: Limit sys_mount to only request filesystem modules prevents mount -t cifs from working
Date: Tue, 12 Mar 2013 02:31:14 +1030	[thread overview]
Message-ID: <513DFFCA.6010304@internode.on.net> (raw)
In-Reply-To: <87obeqnjlm.fsf@xmission.com>



Eric W. Biederman wrote, on 12/03/13 00:07:
> Arthur Marsh<arthur.marsh@internode.on.net>  writes:
>
>> Hi, I found that Linux kernel 3.9.0-rc2 would not mount a remote cifs
>> filesystem, and ran a git bisect which identified the following
>> commit:
>>
>> Is there a patch already present somewhere to fix this problem?
>>
>
> Grr.  It was in linux-next for nearly a week and I checked an double
> checked that patch.
>
> This should fix it.
>
> Eric
>
>
> diff --git a/fs/cifs/cifsfs.c b/fs/cifs/cifsfs.c
> index 1a052c0..3cf8a15 100644
> --- a/fs/cifs/cifsfs.c
> +++ b/fs/cifs/cifsfs.c
> @@ -777,6 +777,7 @@ struct file_system_type cifs_fs_type = {
>   	.kill_sb = cifs_kill_sb,
>   	/*  .fs_flags */
>   };
> +MODULE_ALIAS_FS("cifs");
>   const struct inode_operations cifs_dir_inode_ops = {
>   	.create = cifs_create,
>   	.atomic_open = cifs_atomic_open,
>

Confirmed... cifs mounts now work again thanks.

Regards,

Arthur.

      reply	other threads:[~2013-03-11 16:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-11 12:57 fs: Limit sys_mount to only request filesystem modules prevents mount -t cifs from working Arthur Marsh
2013-03-11 13:37 ` Eric W. Biederman
2013-03-11 16:01   ` Arthur Marsh [this message]

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=513DFFCA.6010304@internode.on.net \
    --to=arthur.marsh@internode.on.net \
    --cc=ebiederm@xmission.com \
    --cc=keescook@google.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=serge.hallyn@canonical.com \
    /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