LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Felix Blanke <felixblanke@gmail.com>
To: Milan Broz <mbroz@redhat.com>
Cc: Chris Samuel <chris@csamuel.org>,
kreijack@inwind.it, linux-btrfs@vger.kernel.org,
Linux Kernel <linux-kernel@vger.kernel.org>,
Hugo Mills <hugo-lkml@carfax.org.uk>
Subject: Re: LOOP_GET_STATUS(64) truncates pathnames to 64 chars (was Re: Bug in mkfs.btrfs?!)
Date: Fri, 11 Feb 2011 20:41:05 +0100 [thread overview]
Message-ID: <AANLkTi=AnavGD9s7sQdNGcgjKNUdiEhFZyLsyc0ROpL7@mail.gmail.com> (raw)
In-Reply-To: <4D558EA7.2070707@redhat.com>
Yeah, for me its loop-aes.
Ah ok, didn't knew that it replaces that whole loop thing :)
Felix
On Feb 11, 2011 8:32 PM, "Milan Broz" <mbroz@redhat.com> wrote:
> On 02/11/2011 08:23 PM, Felix Blanke wrote:
>> What do you mean with "configured"?
>>
>> I'm using loop devices with loop aes, and I've looked into /sys for a device which is actually in use.
>
> Ehm. It is really Loop-AES?
>
> Then ask author to backport it there, Loop-AES is not mainline code.
> He usually replaces the whole upstream loop implementation with old patched version.
>
> Milan
prev parent reply other threads:[~2011-02-11 19:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110122144513.GA2539@scooter>
[not found] ` <20110122145222.GB2539@scooter>
[not found] ` <20110122151124.GC29985@carfax.org.uk>
[not found] ` <20110122155612.GA3664@scooter>
[not found] ` <20110123181827.GF29985@carfax.org.uk>
[not found] ` <4D3CA568.7050506@libero.it>
[not found] ` <20110124130104.GA7354@scooter>
2011-01-25 0:15 ` Chris Samuel
2011-02-10 12:29 ` Petr Uzel
2011-02-11 13:04 ` Felix Blanke
2011-02-11 18:59 ` Milan Broz
[not found] ` <AANLkTi=Arg-09F0DXsWNhsYgyPar=rKs7G_OQG2uMm4f@mail.gmail.com>
2011-02-11 19:31 ` Milan Broz
2011-02-11 19:41 ` Felix Blanke [this message]
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='AANLkTi=AnavGD9s7sQdNGcgjKNUdiEhFZyLsyc0ROpL7@mail.gmail.com' \
--to=felixblanke@gmail.com \
--cc=chris@csamuel.org \
--cc=hugo-lkml@carfax.org.uk \
--cc=kreijack@inwind.it \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbroz@redhat.com \
--subject='Re: LOOP_GET_STATUS(64) truncates pathnames to 64 chars (was Re: Bug in mkfs.btrfs?'\!')' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).