All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>
Subject: [PATCH 0/2] Add more sys_array error handling
Date: Mon, 30 Nov 2015 17:27:02 +0100	[thread overview]
Message-ID: <cover.1448900173.git.dsterba@suse.com> (raw)

Fix for Vegard Nossum's report [1]. I found an older report in our bugzilla, so
there goes also Jiri's reported-by.

[1] http://article.gmane.org/gmane.comp.file-systems.btrfs/50230

David Sterba (2):
  btrfs: handle invalid num_stripes in sys_array
  btrfs: verbose error when we find an unexpected item in sys_array

 fs/btrfs/volumes.c | 11 +++++++++++
 1 file changed, 11 insertions(+)

-- 
2.6.2

--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-

             reply	other threads:[~2015-11-30 16:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-30 16:27 David Sterba [this message]
2015-11-30 16:27 ` [PATCH 1/2] btrfs: handle invalid num_stripes in sys_array David Sterba
2015-11-30 16:27   ` David Sterba
2015-11-30 16:27 ` [PATCH 2/2] btrfs: verbose error when we find an unexpected item " David Sterba

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=cover.1448900173.git.dsterba@suse.com \
    --to=dsterba@suse.com \
    --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 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.