Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: Julian Sikorski <belegdol@gmail.com>
To: ronnie sahlberg <ronniesahlberg@gmail.com>
Cc: CIFS <linux-cifs@vger.kernel.org>
Subject: Re: kernel-5.18.8 breaks cifs mounts
Date: Thu, 30 Jun 2022 19:41:48 +0200	[thread overview]
Message-ID: <fee59438-7b4a-0a24-f116-07c2ac39a3ad@gmail.com> (raw)
In-Reply-To: <CAN05THTbuBSF6HXh5TAThchJZycU1AwiQkA0W7hDwCwKOF+4kw@mail.gmail.com>



Am 30.06.22 um 19:02 schrieb ronnie sahlberg:
> On Fri, 1 Jul 2022 at 03:00, Julian Sikorski <belegdol@gmail.com> wrote:
>>
>> Hi list,
>>
>> it appears that kernel 5.18.8 breaks cifs mounts on my machine. With
>> 5.18.7, everything works fine. With 5.18.8, I am getting:
>>
>> $ sudo mount /mnt/openmediavault/
>> mount error(22): Invalid argument
>> Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel
>> log messages (dmesg)
>>
>> The relevant /etc/fstab line is:
>>
>> //odroidxu4.local/julian /mnt/openmediavault    cifs
>> credentials=/home/julas/.credentials,uid=julas,gid=julas,vers=3.1.1,nobrl,_netdev,auto
>> 0 0
>>
>> Is this a known problem?
> 
> What is the output in dmesg ?
> 
Not much is there:

Jun 30 18:19:34 snowball3 kernel: CIFS: Attempting to mount 
\\odroidxu4.local\julian

Jun 30 18:19:34 snowball3 kernel: CIFS: VFS: cifs_mount failed w/return 
code = -22


I tried reverting 16d5d91 as it was the only commit referencing smb, but 
it did not help unfortunately.

Best regards,
Julian

  reply	other threads:[~2022-06-30 17:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-30 16:47 kernel-5.18.8 breaks cifs mounts Julian Sikorski
2022-06-30 17:02 ` ronnie sahlberg
2022-06-30 17:41   ` Julian Sikorski [this message]
2022-06-30 17:55     ` Paulo Alcantara
2022-06-30 18:11       ` Julian Sikorski
2022-06-30 18:28         ` Paulo Alcantara
2022-06-30 19:12           ` Julian Sikorski
2022-06-30 20:32             ` Enzo Matsumiya
2022-07-04  8:12               ` Shyam Prasad N
2022-07-04 16:30                 ` Julian Sikorski
     [not found]               ` <CAH2r5mtVwZggJ9Fi0zsK5hCci4uxee-kOSC3brb56xpb0_xn7w@mail.gmail.com>
     [not found]                 ` <56afe80b-bf6a-2508-063a-7b091cdbbe0f@gmail.com>
     [not found]                   ` <CAH2r5mvoyhZGjf_wgvjgmkCz=+2iDxCSpbyJ79NMtpE1Ecjdnw@mail.gmail.com>
     [not found]                     ` <fccdb4af-697e-b7fc-6421-f16e9b35bb8e@samba.org>
2022-07-04 16:29                       ` Julian Sikorski
2022-07-05  5:28                         ` Shyam Prasad N
2022-07-05 10:55                           ` Julian Sikorski
2022-07-06 11:18                         ` Julian Sikorski
2022-07-12  4:36                           ` Steve French
2022-07-13 21:25                             ` Georg Müller

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=fee59438-7b4a-0a24-f116-07c2ac39a3ad@gmail.com \
    --to=belegdol@gmail.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=ronniesahlberg@gmail.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