All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: Joe Dougherty <jopado1@yahoo.com>,
	"dm-crypt@saout.de" <dm-crypt@saout.de>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: [dm-crypt] LUKS on a jffs2 partition
Date: Fri, 18 Jul 2014 13:35:18 +0200	[thread overview]
Message-ID: <53C90676.2060501@gmail.com> (raw)
In-Reply-To: <1405636940.30842.YahooMailNeo@web140602.mail.bf1.yahoo.com>

On 07/18/2014 12:42 AM, Joe Dougherty wrote:
> I have a small embedded device with a raw nand flash using jffs2
> filesystem. I want to create a luks container on one of the jffs2
> partitions. Everything seems to work fine until I try to mount the
> file system and I receive the error shown below. Here are the
> commands I used to set this up:
>     cryptsetup luksFormat /dev/mtdblock4 --cipher=aes-cbc-essiv:sha256
>     cryptsetup luksOpen /dev/mtdblock4 efs
> At this point I can perform luksDump and all looks OK and the /dev/mapper/efs exists. So I continue to create filesystem:
>     mkfs.jffs2  -p -l --eraseblock=0x20000 --no-cleanmarkers --pagesize=0x800 -r ./userdata -o /dev/mapper/efs
> Now the mount fails:
>     mount -o loud -t jffs2 /dev/mapper/efs /mnt
>     MTD: Attempt to mount non-MTD device "/dev/mapper/efs"
>     mount: mounting /dev/mapper/efs on /mnt failed: Invalid argument
> 
> I have used similar commands successfully for non-jffs2 filesystems. Is this possible with jffs2? Any help appreciated.
> Here's some additional version info:
> cryptsetup --version
> cryptsetup 1.6.2
> dmsetup --version
> Library version:   1.02.76 (2012-08-07)
> Driver version:    4.20.0
> uname -a
> Linux m-1138 3.0.15+m-1138+gecbbdf0 #1 Tue Jul 8 08:57:12 MST 2014 armv7l GNU/Linux

As you already found, there is a similar bug report
https://code.google.com/p/cryptsetup/issues/detail?id=203

In this case it is almost for sure kernel bug, so maybe reporting it
to appropriate kernel list (perhaps jffs related) would be better.
(Adding dm-devel, maybe someone could help as well.)

Milan

WARNING: multiple messages have this Message-ID (diff)
From: Milan Broz <gmazyland-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Joe Dougherty <jopado1-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>,
	"dm-crypt-4q3lyFh4P1g@public.gmane.org"
	<dm-crypt-4q3lyFh4P1g@public.gmane.org>
Cc: device-mapper development
	<dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: LUKS on a jffs2 partition
Date: Fri, 18 Jul 2014 13:35:18 +0200	[thread overview]
Message-ID: <53C90676.2060501@gmail.com> (raw)
In-Reply-To: <1405636940.30842.YahooMailNeo-mhNdJOJujDYR8UyDmTZ/NZEhsgyP+Z75VpNB7YpNyf8@public.gmane.org>

On 07/18/2014 12:42 AM, Joe Dougherty wrote:
> I have a small embedded device with a raw nand flash using jffs2
> filesystem. I want to create a luks container on one of the jffs2
> partitions. Everything seems to work fine until I try to mount the
> file system and I receive the error shown below. Here are the
> commands I used to set this up:
>     cryptsetup luksFormat /dev/mtdblock4 --cipher=aes-cbc-essiv:sha256
>     cryptsetup luksOpen /dev/mtdblock4 efs
> At this point I can perform luksDump and all looks OK and the /dev/mapper/efs exists. So I continue to create filesystem:
>     mkfs.jffs2  -p -l --eraseblock=0x20000 --no-cleanmarkers --pagesize=0x800 -r ./userdata -o /dev/mapper/efs
> Now the mount fails:
>     mount -o loud -t jffs2 /dev/mapper/efs /mnt
>     MTD: Attempt to mount non-MTD device "/dev/mapper/efs"
>     mount: mounting /dev/mapper/efs on /mnt failed: Invalid argument
> 
> I have used similar commands successfully for non-jffs2 filesystems. Is this possible with jffs2? Any help appreciated.
> Here's some additional version info:
> cryptsetup --version
> cryptsetup 1.6.2
> dmsetup --version
> Library version:   1.02.76 (2012-08-07)
> Driver version:    4.20.0
> uname -a
> Linux m-1138 3.0.15+m-1138+gecbbdf0 #1 Tue Jul 8 08:57:12 MST 2014 armv7l GNU/Linux

As you already found, there is a similar bug report
https://code.google.com/p/cryptsetup/issues/detail?id=203

In this case it is almost for sure kernel bug, so maybe reporting it
to appropriate kernel list (perhaps jffs related) would be better.
(Adding dm-devel, maybe someone could help as well.)

Milan
_______________________________________________
dm-crypt mailing list
dm-crypt-4q3lyFh4P1g@public.gmane.org
http://www.saout.de/mailman/listinfo/dm-crypt

  reply	other threads:[~2014-07-18 11:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-17 22:42 [dm-crypt] LUKS on a jffs2 partition Joe Dougherty
2014-07-18 11:35 ` Milan Broz [this message]
2014-07-18 11:35   ` Milan Broz
2014-08-01  9:26   ` [dm-crypt] " Milan Broz
2014-08-01  9:26     ` Milan Broz

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=53C90676.2060501@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=dm-crypt@saout.de \
    --cc=dm-devel@redhat.com \
    --cc=jopado1@yahoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.