linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Vyacheslav Dubeyko <slava@dubeyko.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-fsdevel@vger.kernel.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v2] hfsplus: avoid crash on failed block map free
Date: Tue, 13 Nov 2012 14:34:44 -0800	[thread overview]
Message-ID: <20121113143444.f8d4bbc3.akpm@linux-foundation.org> (raw)
In-Reply-To: <1352799065.2443.3.camel@slavad-ubuntu>

On Tue, 13 Nov 2012 13:31:05 +0400
Vyacheslav Dubeyko <slava@dubeyko.com> wrote:

> If the read fails we kmap an error code. This doesn't end well. Instead print a critical error and pray. This mirrors the rest of the fs behaviour with critical error cases.
> 
> ...
>
> index 4cfbe2e..6feefc0 100644
> --- a/fs/hfsplus/bitmap.c
> +++ b/fs/hfsplus/bitmap.c
> @@ -176,12 +176,14 @@ int hfsplus_block_free(struct super_block *sb, u32 offset, u32 count)
>  	dprint(DBG_BITMAP, "block_free: %u,%u\n", offset, count);
>  	/* are all of the bits in range? */
>  	if ((offset + count) > sbi->total_blocks)
> -		return -2;
> +		return -ENOENT;
>  
>  	mutex_lock(&sbi->alloc_mutex);
>  	mapping = sbi->alloc_file->i_mapping;
>  	pnr = offset / PAGE_CACHE_BITS;
>  	page = read_mapping_page(mapping, pnr, NULL);
> +	if (IS_ERR(page))
> +		goto kaboom;
>  	pptr = kmap(page);
>  	curr = pptr + (offset & (PAGE_CACHE_BITS - 1)) / 32;
>  	end = pptr + PAGE_CACHE_BITS / 32;
> @@ -214,6 +216,8 @@ int hfsplus_block_free(struct super_block *sb, u32 offset, u32 count)
>  		set_page_dirty(page);
>  		kunmap(page);
>  		page = read_mapping_page(mapping, ++pnr, NULL);
> +		if (IS_ERR(page))
> +			goto kaboom;
>  		pptr = kmap(page);
>  		curr = pptr;
>  		end = pptr + PAGE_CACHE_BITS / 32;
> @@ -232,4 +236,11 @@ out:
>  	mutex_unlock(&sbi->alloc_mutex);
>  
>  	return 0;
> +
> +kaboom:
> +	printk(KERN_CRIT "hfsplus: unable to mark blocks free: error %ld\n",
> +			PTR_ERR(page));
> +	mutex_unlock(&sbi->alloc_mutex);
> +
> +	return -EIO;
>  }

It looks better than what we currently have!

The code is missing a flush_dcache_page()?  We should have one in there
after the CPU has modified userspace-mappable page contents.


btw, I still have question marks over your earlier patches:

hfsplus-add-on-disk-layout-declarations-related-to-attributes-tree.patch
hfsplus-add-functionality-of-manipulating-by-records-in-attributes-tree.patch
hfsplus-rework-functionality-of-getting-setting-and-deleting-of-extended-attributes.patch
hfsplus-add-support-of-manipulation-by-attributes-file.patch
hfsplus-add-support-of-manipulation-by-attributes-file-checkpatch-fixes.patch
hfsplus-code-style-fixes-reworked-support-of-extended-attributes.patch

Christoph sounded unhappy, but the review discussion petered out?


  reply	other threads:[~2012-11-13 22:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-13  9:31 [PATCH v2] hfsplus: avoid crash on failed block map free Vyacheslav Dubeyko
2012-11-13 22:34 ` Andrew Morton [this message]
2012-11-14 11:24   ` Christoph Hellwig
2012-11-15  7:07     ` Vyacheslav Dubeyko
2012-11-15  9:17       ` Christoph Hellwig
2012-11-15  9:31         ` Vyacheslav Dubeyko
2012-11-14 12:50   ` Vyacheslav Dubeyko
2012-12-18 22:47     ` Andrew Morton
2012-12-19  6:26       ` Vyacheslav Dubeyko
2012-12-19  6:29         ` Andrew Morton
2012-12-19  6:42           ` Vyacheslav Dubeyko
2012-12-19 14:09             ` Christoph Hellwig
2012-12-19 14:15               ` Vyacheslav Dubeyko

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=20121113143444.f8d4bbc3.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=slava@dubeyko.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).