Bug 1045840

Summary:	Module cryptoloop is absent in config of 3.12 kernel
Product:	[Fedora] Fedora	Reporter:	ceguhaku
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	19	CC:	fc-bugzilla, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, mail, michele
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-01-06 13:48:47 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description ceguhaku 2013-12-22 13:12:31 UTC

Description of problem:

I need to use realcrypt, but it can not to mount device without cryptoloop module. Realcrypt return error "failed to set up a loop device". In 3.11 kernel configuration this module was present and I have no problem.

Please, rebuild kernel 3.12 with this module to solve the problem.

Comment 1 Michele Baldessari 2013-12-25 22:22:55 UTC

This was done on purpose via:
https://bugzilla.redhat.com/show_bug.cgi?id=896160

Comment 2 Pavel Urban 2013-12-26 18:31:30 UTC

(In reply to Michele Baldessari from comment #1)
> This was done on purpose via:
> https://bugzilla.redhat.com/show_bug.cgi?id=896160

Well, I've probably met this 'fix', too.

[root@localhost home]# losetup /dev/loop0 /home/cryptohome
losetup: /dev/loop0: failed to set up loop device: No such file or directory
[root@localhost home]# losetup -f
/dev/loop0
[root@localhost home]# losetup /dev/loop0 /home/cryptohome
[root@localhost home]# 

The comment in https://bugzilla.redhat.com/show_bug.cgi?id=896160 says that losetup should've been already modified to work this way, but I'm afraid it wasn't, at least on my Fedora 19...

[root@localhost home]# uname -a
Linux localhost.localdomain 3.12.5-200.fc19.x86_64 #1 SMP Tue Dec 17 22:21:14 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
[root@localhost home]# rpm -qf `which losetup`
util-linux-2.23.2-4.fc19.x86_64
[root@localhost home]# cat /etc/redhat-release 
Fedora release 19 (Schrödinger’s Cat)

It seems to me like the bug in losetup, then.

Comment 3 Pavel Urban 2013-12-26 18:43:32 UTC

> It seems to me like the bug in losetup, then.

OK, I can accept this as a 'change in behavior'. It works, but not the way I am expecting it. At least it would be convenient to have the command-line switch to losetup that returns the number of automagically created device...

Comment 4 Michele Baldessari 2013-12-26 19:34:13 UTC

This is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1019440 which admittedly is for F20 but the issue is the same

Comment 5 Pavel Urban 2013-12-26 20:08:04 UTC

(In reply to Pavel Urban from comment #3)
> > It seems to me like the bug in losetup, then.
> 
> OK, I can accept this as a 'change in behavior'. It works, but not the way I
> am expecting it. At least it would be convenient to have the command-line
> switch to losetup that returns the number of automagically created device...

Ah! In fact, there IS a command-line switch for this ;-)

Anyway, losetup's man page probably should be updated to reflect these changes. Something like:

Note that in kernel 3.12 and newer there are no pre-generated loop devices. When setting up loop device, you should use 'losetup -f --show file' and use the output from this command as your new loop device. When you try to use something like 'losetup /dev/loop0 file', you'll probably get ENOENT and 'failed to set up loop device: No such file or directory', because there is no /dev/loop0 yet.


For me the problem is solved - fortunately I just had to rewrite several lines in my script.

Comment 6 Josh Boyer 2014-01-06 13:48:47 UTC


*** This bug has been marked as a duplicate of bug 1019440 ***