All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [Bug 205181] New: kernel panic when accessing btrfs root device with f2fs in kernel
Date: Sun, 13 Oct 2019 13:13:33 +0000	[thread overview]
Message-ID: <bug-205181-202145@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=205181

            Bug ID: 205181
           Summary: kernel panic when accessing btrfs root device with
                    f2fs in kernel
           Product: File System
           Version: 2.5
    Kernel Version: 4.19.76-4.19.79
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: blocking
          Priority: P1
         Component: f2fs
          Assignee: filesystem_f2fs@kernel-bugs.kernel.org
          Reporter: rogan6710@gmail.com
        Regression: No

This happens on kernel versions 4.19.76-4.19.79 on x86_64 (Slackware):
With support for btrfs, f2fs, ext*, xfs and a few others compiled in kernel it
panics when accessing a btrfs root device.
If support for f2fs is removed all works normally on 4.19.79, as does versions
before 4.19.76.
The problem has been verified on different machines by different users.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

             reply	other threads:[~2019-10-13 13:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-13 13:13 bugzilla-daemon [this message]
2019-10-13 14:08 ` [f2fs-dev] [Bug 205181] kernel panic when accessing btrfs root device with f2fs in kernel bugzilla-daemon
2019-10-13 15:49 ` bugzilla-daemon
2019-10-13 16:19 ` bugzilla-daemon
2019-10-19 17:29 ` bugzilla-daemon
2019-10-31 18:14 ` bugzilla-daemon

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=bug-205181-202145@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    /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.