8:44 a.m.
Computer is Thinkpad x260
Uname -a:
Linux rwells-x260 4.13.4-200.fc26.x86_64 #1 SMP Thu Sep 28 20:46:39 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
Just updated from 4.12.14
I was using two Bluetooth devices, mouse & speaker, when I started the
update.
After the update neither would connect.
Rebooting the previous kernel, both connect again
Same for Wayland & Xorg (no surprise)
--
Roger Wells, P.E.
leidos
221 Third St
Newport, RI 02840
401-847-4210 (voice)
401-849-1585 (fax)
roger.k.wells(a)leidos.com
9:10 a.m.
New subject: EXTERNAL: This morning's update & bluetooth
On 10/06/2017 09:45 AM, Wells, Roger K. wrote:
Computer is Thinkpad x260
Uname -a:
Linux rwells-x260 4.13.4-200.fc26.x86_64 #1 SMP Thu Sep 28 20:46:39
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Just updated from 4.12.14
I was using two Bluetooth devices, mouse & speaker, when I started the
update.
After the update neither would connect.
Rebooting the previous kernel, both connect again
Same for Wayland & Xorg (no surprise)
Also just discovered:
Network drives (cifs) that were in use are no longer mountable on the
4.13.4-200 kernel.
Reverting back to 4.12.14-300 and all is well again.
--
Roger Wells, P.E.
leidos
221 Third St
Newport, RI 02840
401-847-4210 (voice)
401-849-1585 (fax)
roger.k.wells(a)leidos.com
10 a.m.
New subject: EXTERNAL: This morning's update & bluetooth
On Fri, 6 Oct 2017 10:10:11 -0400 Wells, Roger K. wrote:
[ ... ]
Also just discovered:
Network drives (cifs) that were in use are no longer mountable on the
4.13.4-200 kernel.
Reverting back to 4.12.14-300 and all is well again.
Same here. Took me some time to revert. Could not imagine a kernel prob.
--Frank
3:56 a.m.
New subject: EXTERNAL: This morning's update & bluetooth
On Fri, Oct 06, 2017 at 03:00:40PM +0000, Frank Elsner wrote:
On Fri, 6 Oct 2017 10:10:11 -0400 Wells, Roger K. wrote:
[ ... ]
> Also just discovered:
> Network drives (cifs) that were in use are no longer mountable on the
> 4.13.4-200 kernel.
> Reverting back to 4.12.14-300 and all is well again.
Same here. Took me some time to revert. Could not imagine a kernel prob.
with 4.13, smb version 1 is deprecated, it now uses version 3 by
default.
Taken from https://lkml.org/lkml/2017/9/3/155
This time it's not really a kernel security issue, but a generic
protocol security issue.
The change in question is simply changing the default cifs behavior:
instead of defaulting to SMB 1.0 (which you really should not use:
just google for "stop using SMB1" or similar), the default cifs mount
now defaults to a rather more modern SMB 3.0.
Now, because you shouldn't have been using SMB1 anyway, this shouldn't
affect anybody. But guess what? It almost certainly does affect some
people, because they blithely continued using SMB1 without really
thinking about it.
And you certainly _can_ continue to use SMB1, but due to the default
change, now you need to be *aware* of it. You may need to add an
explicit "vers=1.0" to your mount options in /etc/fstab or similar if
you *really* want SMB1.
adding vers=1.0 to mount options is what you want to do.
--
Matthias Runge <mrunge(a)matthias-runge.de>
8:28 a.m.
New subject: EXTERNAL: This morning's update & bluetooth
On 10/14/2017 04:58 AM, Matthias Runge wrote:
On Fri, Oct 06, 2017 at 03:00:40PM +0000, Frank Elsner wrote:
> On Fri, 6 Oct 2017 10:10:11 -0400 Wells, Roger K. wrote:
>
> [ ... ]
>> Also just discovered:
>> Network drives (cifs) that were in use are no longer mountable on the
>> 4.13.4-200 kernel.
>> Reverting back to 4.12.14-300 and all is well again.
> Same here. Took me some time to revert. Could not imagine a kernel prob.
with 4.13, smb version 1 is deprecated, it now uses version 3 by
default.
Taken from https://lkml.org/lkml/2017/9/3/155
This time it's not really a kernel security issue, but a generic
protocol security issue.
The change in question is simply changing the default cifs behavior:
instead of defaulting to SMB 1.0 (which you really should not use:
just google for "stop using SMB1" or similar), the default cifs mount
now defaults to a rather more modern SMB 3.0.
Now, because you shouldn't have been using SMB1 anyway, this shouldn't
affect anybody. But guess what? It almost certainly does affect some
people, because they blithely continued using SMB1 without really
thinking about it.
And you certainly _can_ continue to use SMB1, but due to the default
change, now you need to be *aware* of it. You may need to add an
explicit "vers=1.0" to your mount options in /etc/fstab or similar if
you *really* want SMB1.
adding vers=1.0 to mount options is what you want to do.
yes, samba mounts still do not work.
I did google for "stop using SMB1" and only got Windows references. How
does one adopt/upgrade to SMB 3.0?
The Bluetooth problems that motivated the original post are different,
not fixed.
Devices connect (sometimes) but erratically disconnect and reconnect
until the machine had to be restarted via the power switch.
I will keep at it and try to get something repeatable to report.
Back to 4.12.14 for now in order to be able to do some work.
--
Roger Wells, P.E.
leidos
221 Third St
Newport, RI 02840
401-847-4210 (voice)
401-849-1585 (fax)
roger.k.wells(a)leidos.com
12:12 p.m.
New subject: EXTERNAL: This morning's update & bluetooth
On Monday, October 16, 2017, 9:30:00 AM EDT, Wells, Roger K. <wellsr(a)leidos.com>
wrote:
On 10/14/2017 04:58 AM, Matthias Runge wrote:
On Fri, Oct 06, 2017 at 03:00:40PM +0000, Frank Elsner wrote:
> On Fri, 6 Oct 2017 10:10:11 -0400 Wells, Roger K. wrote:
>
> [ ... ]
>> Also just discovered:
>> Network drives (cifs) that were in use are no longer mountable on the
>> 4.13.4-200 kernel.
>> Reverting back to 4.12.14-300 and all is well again.
> Same here. Took me some time to revert. Could not imagine a kernel prob.
with 4.13, smb version 1 is deprecated, it now uses version 3 by
default.
Taken from https://lkml.org/lkml/2017/9/3/155
This time it's not really a kernel security issue, but a generic
protocol security issue.
The change in question is simply changing the default cifs behavior:
instead of defaulting to SMB 1.0 (which you really should not use:
just google for "stop using SMB1" or similar), the default cifs mount
now defaults to a rather more modern SMB 3.0.
Now, because you shouldn't have been using SMB1 anyway, this shouldn't
affect anybody. But guess what? It almost certainly does affect some
people, because they blithely continued using SMB1 without really
thinking about it.
And you certainly _can_ continue to use SMB1, but due to the default
change, now you need to be *aware* of it. You may need to add an
explicit "vers=1.0" to your mount options in /etc/fstab or similar if
you *really* want SMB1.
adding vers=1.0 to mount options is what you want to do.
yes, samba mounts still do not work.
I did google for "stop using SMB1" and only got Windows references. How
does one adopt/upgrade to SMB 3.0?
The Bluetooth problems that motivated the original post are different,
not fixed.
Devices connect (sometimes) but erratically disconnect and reconnect
until the machine had to be restarted via the power switch.
I will keep at it and try to get something repeatable to report.
Back to 4.12.14 for now in order to be able to do some work.
--
Roger Wells, P.E.
Manufacturers don't seem to be upgrading the firmware on network storage systems.
Still need SMB1 to attach to various appliances.
_______________________________________________users mailing list --
users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
9:35 a.m.
New subject: EXTERNAL: This morning's update & bluetooth
On Fri, 6 Oct 2017 10:10:11 -0400 Wells, Roger K. wrote:
[ Bluetooth problem not cited ]
Also just discovered:
Network drives (cifs) that were in use are no longer mountable on the
4.13.4-200 kernel.
Reverting back to 4.12.14-300 and all is well again.
Problem still exists with 4.13.5-200.
--Frank
2:08 p.m.
New subject: EXTERNAL: This morning's update & bluetooth
On 12/10/2017 01:35, Frank Elsner wrote:
On Fri, 6 Oct 2017 10:10:11 -0400 Wells, Roger K. wrote:
[ Bluetooth problem not cited ]
> Also just discovered:
> Network drives (cifs) that were in use are no longer mountable on the
> 4.13.4-200 kernel.
> Reverting back to 4.12.14-300 and all is well again.
Problem still exists with 4.13.5-200.
I'm using a cifs network drive in Fedora 26 with kernel 4.13.10-200 and
using option vers=1.0 on the mount entry in /etc/fstab allows the drive
to be mounted. Without the parameter the mount request says the drive is
down. The drive is attached to my router and I am using ethernet to
access the network.
regards,
Steve
>
>
> --Frank
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
2360
days inactive
2391
days old
7 comments
5 participants
participants (5)
-
Frank Elsner -
Matthias Runge -
Robert McBroom -
Stephen Morris -
Wells, Roger K.