Bug 1389980 - sun4i-ss 1c15000.crypto-engine: ERROR: Empty IV
Summary: sun4i-ss 1c15000.crypto-engine: ERROR: Empty IV
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: ARMTracker
TreeView+ depends on / blocked
 
Reported: 2016-10-30 10:21 UTC by Daniel L.
Modified: 2017-02-17 07:33 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-17 07:33:06 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Daniel L. 2016-10-30 10:21:31 UTC
Description of problem:
Mounting a cifs share with option sec=ntlm gives the following error:
kernel: sun4i-ss 1c15000.crypto-engine: ERROR: Empty IV
kernel: CIFS VFS: could not encrypt crypt key rc: -22
kernel: CIFS VFS: Error -22 during NTLM authentication
kernel: CIFS VFS: Send error in SessSetup = -22
kernel: CIFS VFS: cifs_mount failed w/return code = -22

Hardware is a Cubietruck. ntlmssp works.

Version-Release number of selected component (if applicable):
Kernel 4.7.9-200.fc24.armv7hl on a Cubietruck (Allwinner A20 SoC)

How reproducible:
Mount a cifs share with sec=ntlm like in the following command:
mount -t cifs -o username=user,sec=ntlm //servername./foldername /mountpoint

Actual results:
The mount command results in a kernel error

Expected results:
Mounted cifs share

Comment 1 Peter Robinson 2016-10-31 18:18:07 UTC
Does it work if you black list the sun4i_ss driver?

Add a file called /etc/modprobe.d/sun4i.conf

with the line:
blacklist sun4i_ss

Comment 2 Daniel L. 2016-10-31 18:35:01 UTC
Hi,

ntlm as well as ntlmssp both work when the sun4i_ss driver is blacklisted.

Comment 3 Peter Robinson 2017-02-16 11:00:07 UTC
Are you still seeing this with 4.9.x kernels?

Comment 4 Daniel L. 2017-02-16 19:25:20 UTC
No, I don't see this anymore. The system is currently running kernel 4.9.9-200.fc25.armv7hl.

Comment 5 Peter Robinson 2017-02-17 07:33:06 UTC
thanks for the update


Note You need to log in before you can comment on or make changes to this bug.