From: Philipp Hahn <pmhahn@pmhahn.de>
To: Philipp Hahn <hahn@univention.de>, linux-btrfs@vger.kernel.org
Cc: Qu Wenruo <quwenruo@cn.fujitsu.com>, David Sterba <dsterba@suse.cz>
Subject: Re: [PATCH 0/2] More nritems range checking
Date: Wed, 2 Aug 2017 09:28:15 +0200 [thread overview]
Message-ID: <cfebd4ee-adfe-9ef9-33db-2ddb01001a79@pmhahn.de> (raw)
In-Reply-To: <cover.1496397503.git.hahn@univention.de>
Hello,
Am 02.06.2017 um 12:08 schrieb Philipp Hahn:
> thank you for applying my last patch, but regarding my corrputed file system I
> found two other cases were btrfs crashes:
> - btrfs_del_items() was overlooked by me
> - deleting from an empty node
>
> Find attached two patches to improve that.
> Please check the second patch hunk 2, as I'm unsure if "mid == nritems" is valid.
>
> (If someone can give me a hand on how to get my FS fixed again, I would
> appreciate that.)
>
> Philipp Hahn (2):
> btrfs-progs: Check slot + nr >= nritems overflow
> btrfs-progs: Check nritems under-/overflow
>
> ctree.c | 13 +++++++------
> 1 file changed, 7 insertions(+), 6 deletions(-)
Ping?
Philipp
next prev parent reply other threads:[~2017-08-02 7:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 17:00 [PATCHv2] btrfs-progs: Fix slot >= nritems Philipp Hahn
2017-05-29 18:19 ` David Sterba
2017-06-02 10:08 ` [PATCH 0/2] More nritems range checking Philipp Hahn
2017-08-02 7:28 ` Philipp Hahn [this message]
2017-06-02 10:08 ` [PATCH 1/2] btrfs-progs: Check slot + nr >= nritems overflow Philipp Hahn
2017-06-02 10:08 ` [PATCH 2/2] btrfs-progs: Check nritems under-/overflow Philipp Hahn
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=cfebd4ee-adfe-9ef9-33db-2ddb01001a79@pmhahn.de \
--to=pmhahn@pmhahn.de \
--cc=dsterba@suse.cz \
--cc=hahn@univention.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.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;
as well as URLs for NNTP newsgroup(s).