From: Martin <m_btrfs@ml1.co.uk>
To: linux-btrfs@vger.kernel.org
Subject: Re: Can anyone boot a system using btrfs root with linux 3.14 or newer? - RESOLVED
Date: Sun, 27 Apr 2014 17:00:58 +0100 [thread overview]
Message-ID: <ljj9jr$jmn$1@ger.gmane.org> (raw)
In-Reply-To: <001501cf6210$4142a840$c3c7f8c0$@petrovi.no-ip.info>
On 27/04/14 13:00, Пламен Петров wrote:
> The problem reported in this thread has been RESOLVED.
>
> It's not BTRFS's fault.
>
> Debugging on my part led to the actual problem in do_mounts.c - some
> filesystems mount routines return error codes other than 0, EACCES
> and EINVAL and such return codes result in the kernel panicking
> without trying to mount root with all of the available filesystems.
>
> Patch is available as attachment to bug 74901 -
> https://bugzilla.kernel.org/show_bug.cgi?id=74901 . The bugentry
> documents how I managed to find the problem.
Well deduced and that looks to be a good natural clean fix.
My only question is: What was the original intent to deliberately fail
if something other than EACCES or EINVAL were reported?
> Also, the patch has been sent to the linux kernel mailing list - see
> http://news.gmane.org/find-root.php?group=gmane.linux.kernel&article=1691881
> Hopefully, it will find its way into the kernel, and later on - in
> stable releases.
That all looks very good and very thorough.
> Thanks to you all! ------------------------------ Plamen Petrov
Thanks to you for chasing it through!
AND for posting the "Resolved" to let everyone know. :-)
Regards,
Martin
next prev parent reply other threads:[~2014-04-27 16:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-27 12:00 Can anyone boot a system using btrfs root with linux 3.14 or newer? - RESOLVED Пламен Петров
2014-04-27 16:00 ` Martin [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-05-01 20:27 Пламен Петров
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='ljj9jr$jmn$1@ger.gmane.org' \
--to=m_btrfs@ml1.co.uk \
--cc=linux-btrfs@vger.kernel.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 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).