From: Roman Mamedov <rm@romanrm.net>
To: WorMzy Tykashi <wormzy.tykashi@gmail.com>
Cc: Filipe Manana <fdmanana@gmail.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs module dependencies broken in 3.14?
Date: Sat, 7 Jun 2014 00:53:17 +0600 [thread overview]
Message-ID: <20140607005317.077071e0@natsu> (raw)
In-Reply-To: <CALOYprW2R7iN0j=M6py0pbOkibbyob5L7KXHtmT92-32wVYMdw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 852 bytes --]
On Fri, 6 Jun 2014 19:31:37 +0100
WorMzy Tykashi <wormzy.tykashi@gmail.com> wrote:
> My solution was to write a patch for mkinitcpio (Arch initrd creation
> tool) [1] so that it explicitly adds the crc32c module to the initrd
> if btrfs is needed. I imagine it wouldn't be difficult to add the same
> logic to debian's initrd creation tool. IIRC it already does something
> similar in other cases where there's an invisible dependency like
> this.
It was "visible" in 3.13, see the Debian bug link, there are modinfo of the
3.13 and 3.14 modules compared side by side. I wonder is there really no way to
make it show up in the actual module dependencies as before?
To me patching initrd creation tools to special-case "if btrfs then add crc32"
seems to be a really bizarre way of dealing with the issue.
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-06-06 18:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 14:40 btrfs module dependencies broken in 3.14? Roman Mamedov
2014-06-06 15:41 ` Filipe David Manana
2014-06-06 18:31 ` WorMzy Tykashi
2014-06-06 18:53 ` Roman Mamedov [this message]
2014-06-06 20:05 ` WorMzy Tykashi
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=20140607005317.077071e0@natsu \
--to=rm@romanrm.net \
--cc=fdmanana@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wormzy.tykashi@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox