From: Suresh Jayaraman <sjayaraman@suse.de>
To: Sven-Haegar Koch <haegar@sdinet.de>
Cc: Steve French <sfrench@samba.org>,
linux-cifs@vger.kernel.org,
Linux-Kernel-Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: 3.0-rc+git OOPS losetup on cifs
Date: Thu, 07 Jul 2011 12:55:35 +0530 [thread overview]
Message-ID: <4E155F6F.6070506@suse.de> (raw)
In-Reply-To: <alpine.DEB.2.02.1107042132500.18300@aurora>
On 07/05/2011 01:18 AM, Sven-Haegar Koch wrote:
> hello,
>
> Since a short while (I know it worked with 3.0-rc1) loopback-mounting an
> image on a samba server mounted with cifs oopses the kernel.
>
> Szenario:
> - Client system: Thinkpad T60, 32bit, Debian Unstable
> - Server system: Lacie edmini NAS device, exporting 500GB disk with
> samba, 450GB crypto image file on it
> - mount -t cifs -o username=backups,uid=1000,gid=0,file_mode=0664,dir_mode=0775,rw //192.168.10.98/backups /mnt/real-backups
> - losetup /dev/loop7 /mnt/real-backups/loop.img
> - cryptsetup luksOpen /dev/loop7 cifsloop
> - mount -t ext4 -o rw,noatime,delalloc,barrier=0 /dev/mapper/cifsloop /mnt/backups
>
> This worked since ages, but since some time after 2.6.39 (last test
> with 3.0-rc5+git ba466c74d99b91b2) this throws a kernel oops at the
> "losetup" stage.
I couldn't reproduce this with 3.0-rc6 with a smaller image file (1GB).
But I see no relevant fixes between -rc5 and -rc6.
Can you try to reproduce the same problem with a smaller non-encrypted file?
Thanks,
--
Suresh Jayaraman
next prev parent reply other threads:[~2011-07-07 7:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-04 19:48 3.0-rc+git OOPS losetup on cifs Sven-Haegar Koch
2011-07-07 7:25 ` Suresh Jayaraman [this message]
[not found] ` <4E155F6F.6070506-l3A5Bk7waGM@public.gmane.org>
2011-07-09 1:21 ` Sven-Haegar Koch
2011-07-09 1:21 ` Sven-Haegar Koch
2011-07-09 13:42 ` Sven-Haegar Koch
2011-07-09 13:42 ` Sven-Haegar Koch
2011-07-09 17:53 ` Steve French
2011-07-09 12:09 ` Maciej Rutecki
2011-07-09 12:09 ` Maciej Rutecki
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=4E155F6F.6070506@suse.de \
--to=sjayaraman@suse.de \
--cc=haegar@sdinet.de \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfrench@samba.org \
/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.