All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: reiserfs-devel@vger.kernel.org
Subject: [Bug 187561] New: Kernel Dump on Write-Access to when Kernel is compiled without Reiserfs-Extended-Attributes-Option
Date: Sun, 13 Nov 2016 22:03:54 +0000	[thread overview]
Message-ID: <bug-187561-695@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 187561
           Summary: Kernel Dump on Write-Access to when Kernel is compiled
                    without Reiserfs-Extended-Attributes-Option
           Product: File System
           Version: 2.5
    Kernel Version: 4.4.31
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: ReiserFS
          Assignee: reiserfs-devel@vger.kernel.org
          Reporter: felix.wiedenroth@gmx.de
        Regression: No

When a custom-kernel is compiled with Reiserfs-Support and the Option "Reiserfs
Extended Attibutes is NOT chosen, the Kernel Crashes on Write-Access to the
Reiserfs-Filesystem. This happens when a Reiserfs is created with default
options using mkfs.reiserfs.

I observed this behaviour with Kernel-Versions 4.4.28 to 4.4.31. 

Works fine if extended-attributes are activated in the Kernel.

Problems is probably, that Kernel does not set / return default Values for the
Extended-Reiserfs-Attributes when option "Extended-Attributes" for Reiserfs is
not compiled in.

Regards,

Felix Wiedenroth

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

             reply	other threads:[~2016-11-13 22:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-13 22:03 bugzilla-daemon [this message]
2016-11-14 10:57 ` [Bug 187561] Kernel Dump on Write-Access to when Kernel is compiled without Reiserfs-Extended-Attributes-Option 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-187561-695@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=reiserfs-devel@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 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.