All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH v2] hfsplus: avoid crash on failed block map free
@ 2012-11-13  9:31 Vyacheslav Dubeyko
  2012-11-13 22:34 ` Andrew Morton
  0 siblings, 1 reply; 13+ messages in thread
From: Vyacheslav Dubeyko @ 2012-11-13  9:31 UTC (permalink / raw)
  To: Alan Cox; +Cc: linux-fsdevel, Andrew Morton

Hi Alan,

Do you agree with second version of the patch?

With the best regards,
Vyacheslav Dubeyko.
--
From: Alan Cox <alan@linux.intel.com>
Subject: [PATCH v2] hfsplus: avoid crash on failed block map free

v1->v2
* Change hardcoded error code on -ENOENT.
* Add return -EIO for the case of kmap error.
* Fix issue with twice mutex unlock.
* Fix issue with printing kmap error message on every call.

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.

Acked-by: Vyacheslav Dubeyko <slava@dubeyko.com>
Signed-off-by: Alan Cox <alan@linux.intel.com>
Signed-off-by: Vyacheslav Dubeyko <slava@dubeyko.com>
---
 fs/hfsplus/bitmap.c |   13 ++++++++++++-
 1 file changed, 12 insertions(+), 1 deletion(-)

diff --git a/fs/hfsplus/bitmap.c b/fs/hfsplus/bitmap.c
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;
 }
-- 
1.7.9.5




^ permalink raw reply related	[flat|nested] 13+ messages in thread

* Re: [PATCH v2] hfsplus: avoid crash on failed block map free
  2012-11-13  9:31 [PATCH v2] hfsplus: avoid crash on failed block map free Vyacheslav Dubeyko
@ 2012-11-13 22:34 ` Andrew Morton
  2012-11-14 11:24   ` Christoph Hellwig
  2012-11-14 12:50   ` Vyacheslav Dubeyko
  0 siblings, 2 replies; 13+ messages in thread
From: Andrew Morton @ 2012-11-13 22:34 UTC (permalink / raw)
  To: Vyacheslav Dubeyko; +Cc: Alan Cox, linux-fsdevel, Christoph Hellwig

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?


^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [PATCH v2] hfsplus: avoid crash on failed block map free
  2012-11-13 22:34 ` Andrew Morton
@ 2012-11-14 11:24   ` Christoph Hellwig
  2012-11-15  7:07     ` Vyacheslav Dubeyko
  2012-11-14 12:50   ` Vyacheslav Dubeyko
  1 sibling, 1 reply; 13+ messages in thread
From: Christoph Hellwig @ 2012-11-14 11:24 UTC (permalink / raw)
  To: Andrew Morton
  Cc: Vyacheslav Dubeyko, Alan Cox, linux-fsdevel, Christoph Hellwig

On Tue, Nov 13, 2012 at 02:34:44PM -0800, Andrew Morton wrote:
> 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?

It really just needs the xattr namespace fixed.  JFS is a good model for
how to expose the legacy OS/2 attributes that are lacking a namespace prefix.

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [PATCH v2] hfsplus: avoid crash on failed block map free
  2012-11-13 22:34 ` Andrew Morton
  2012-11-14 11:24   ` Christoph Hellwig
@ 2012-11-14 12:50   ` Vyacheslav Dubeyko
  2012-12-18 22:47     ` Andrew Morton
  1 sibling, 1 reply; 13+ messages in thread
From: Vyacheslav Dubeyko @ 2012-11-14 12:50 UTC (permalink / raw)
  To: Andrew Morton; +Cc: Alan Cox, linux-fsdevel, Christoph Hellwig

On Tue, 2012-11-13 at 14:34 -0800, Andrew Morton wrote:

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

Yes, I think your comment is precious. But I feel a necessity to analyze
hfsplus driver code more deeply for proper fix of this issue. An
userspace-mappable page content is the main use-case for such fix. But
it exists the multi CPUs use-case. So, I need to think about correctness
of hfsplus driver for such use-case also, I think.  

> 
> 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?
> 

So, as you can see the discussion revives again. :-) And I need to
familiarize with implementation of xattrs in JFS before to answer again.
I had objection that we need to remember about using HFS+ volumes as
under Linux as under Mac OS X. Maybe, JFS implementation of xattrs to
change my vision.

With the best regards,
Vyacheslav Dubeyko.



^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [PATCH v2] hfsplus: avoid crash on failed block map free
  2012-11-14 11:24   ` Christoph Hellwig
@ 2012-11-15  7:07     ` Vyacheslav Dubeyko
  2012-11-15  9:17       ` Christoph Hellwig
  0 siblings, 1 reply; 13+ messages in thread
From: Vyacheslav Dubeyko @ 2012-11-15  7:07 UTC (permalink / raw)
  To: Christoph Hellwig; +Cc: Andrew Morton, Alan Cox, linux-fsdevel

Hi,

On Wed, 2012-11-14 at 12:24 +0100, Christoph Hellwig wrote:
> On Tue, Nov 13, 2012 at 02:34:44PM -0800, Andrew Morton wrote:
> > 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?
> 
> It really just needs the xattr namespace fixed.  JFS is a good model for
> how to expose the legacy OS/2 attributes that are lacking a namespace prefix.

So, likewise JFS model every pure Mac OS X xattr (for example,
com.apple.FinderInfo) will be prefixed with "mac-os-x." during
list_xattr stage. Then this prefix will be excluded for search in
Catalog b-tree during get_xattr and set_xattr calls. And I try to rework
the code for using general dispatching code also.

Do you have any objections? :-)

With the best regards,
Vyacheslav Dubeyko.

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



^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [PATCH v2] hfsplus: avoid crash on failed block map free
  2012-11-15  7:07     ` Vyacheslav Dubeyko
@ 2012-11-15  9:17       ` Christoph Hellwig
  2012-11-15  9:31         ` Vyacheslav Dubeyko
  0 siblings, 1 reply; 13+ messages in thread
From: Christoph Hellwig @ 2012-11-15  9:17 UTC (permalink / raw)
  To: Vyacheslav Dubeyko
  Cc: Christoph Hellwig, Andrew Morton, Alan Cox, linux-fsdevel

On Thu, Nov 15, 2012 at 11:07:39AM +0400, Vyacheslav Dubeyko wrote:
> So, likewise JFS model every pure Mac OS X xattr (for example,
> com.apple.FinderInfo) will be prefixed with "mac-os-x." during
> list_xattr stage. Then this prefix will be excluded for search in
> Catalog b-tree during get_xattr and set_xattr calls. And I try to rework
> the code for using general dispatching code also.
> 
> Do you have any objections? :-)

How about just osx  as a short prefix?  That'll mirror os2. and looks
less awkward.  Otherwise the plan looks good.


^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [PATCH v2] hfsplus: avoid crash on failed block map free
  2012-11-15  9:17       ` Christoph Hellwig
@ 2012-11-15  9:31         ` Vyacheslav Dubeyko
  0 siblings, 0 replies; 13+ messages in thread
From: Vyacheslav Dubeyko @ 2012-11-15  9:31 UTC (permalink / raw)
  To: Christoph Hellwig; +Cc: Andrew Morton, Alan Cox, linux-fsdevel

On Thu, 2012-11-15 at 10:17 +0100, Christoph Hellwig wrote:
> On Thu, Nov 15, 2012 at 11:07:39AM +0400, Vyacheslav Dubeyko wrote:
> > So, likewise JFS model every pure Mac OS X xattr (for example,
> > com.apple.FinderInfo) will be prefixed with "mac-os-x." during
> > list_xattr stage. Then this prefix will be excluded for search in
> > Catalog b-tree during get_xattr and set_xattr calls. And I try to rework
> > the code for using general dispatching code also.
> > 
> > Do you have any objections? :-)
> 
> How about just osx  as a short prefix?  That'll mirror os2. and looks
> less awkward.  Otherwise the plan looks good.
> 

Ok. I agree with "osx." prefix.

With the best regards,
Vyacheslav Dubeyko.

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



^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [PATCH v2] hfsplus: avoid crash on failed block map free
  2012-11-14 12:50   ` Vyacheslav Dubeyko
@ 2012-12-18 22:47     ` Andrew Morton
  2012-12-19  6:26       ` Vyacheslav Dubeyko
  0 siblings, 1 reply; 13+ messages in thread
From: Andrew Morton @ 2012-12-18 22:47 UTC (permalink / raw)
  To: Vyacheslav Dubeyko; +Cc: Alan Cox, linux-fsdevel, Christoph Hellwig

On Wed, 14 Nov 2012 16:50:53 +0400
Vyacheslav Dubeyko <slava@dubeyko.com> wrote:

> On Tue, 2012-11-13 at 14:34 -0800, Andrew Morton wrote:
> 
> [snip]
> > 
> > The code is missing a flush_dcache_page()?  We should have one in there
> > after the CPU has modified userspace-mappable page contents.
> > 
> 
> Yes, I think your comment is precious. But I feel a necessity to analyze
> hfsplus driver code more deeply for proper fix of this issue. An
> userspace-mappable page content is the main use-case for such fix. But
> it exists the multi CPUs use-case. So, I need to think about correctness
> of hfsplus driver for such use-case also, I think.  
> 
> > 
> > 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?
> > 
> 
> So, as you can see the discussion revives again. :-) And I need to
> familiarize with implementation of xattrs in JFS before to answer again.
> I had objection that we need to remember about using HFS+ volumes as
> under Linux as under Mac OS X. Maybe, JFS implementation of xattrs to
> change my vision.

I'm still unclear where we stand with these patches.  Which if any of
these should I merge?

Thanks.

hfsplus-avoid-crash-on-failed-block-map-free.patch
http://ozlabs.org/~akpm/mmots/broken-out/hfsplus-avoid-crash-on-failed-block-map-free.patch

hfsplus-add-osx-prefix-for-handling-namespace-of-mac-os-x-extended-attributes.patch
http://ozlabs.org/~akpm/mmots/broken-out/hfsplus-add-osx-prefix-for-handling-namespace-of-mac-os-x-extended-attributes.patch

hfsplus-add-on-disk-layout-declarations-related-to-attributes-tree.patch
http://ozlabs.org/~akpm/mmots/broken-out/hfsplus-add-on-disk-layout-declarations-related-to-attributes-tree.patch

hfsplus-add-functionality-of-manipulating-by-records-in-attributes-tree.patch
http://ozlabs.org/~akpm/mmots/broken-out/hfsplus-add-functionality-of-manipulating-by-records-in-attributes-tree.patch

hfsplus-rework-functionality-of-getting-setting-and-deleting-of-extended-attributes.patch
http://ozlabs.org/~akpm/mmots/broken-out/hfsplus-rework-functionality-of-getting-setting-and-deleting-of-extended-attributes.patch

hfsplus-add-support-of-manipulation-by-attributes-file.patch
http://ozlabs.org/~akpm/mmots/broken-out/hfsplus-add-support-of-manipulation-by-attributes-file.patch

hfsplus-rework-processing-errors-in-hfsplus_free_extents.patch
http://ozlabs.org/~akpm/mmots/broken-out/hfsplus-rework-processing-errors-in-hfsplus_free_extents.patch

hfsplus-rework-processing-of-hfs_btree_write-returned-error.patch
http://ozlabs.org/~akpm/mmots/broken-out/hfsplus-rework-processing-of-hfs_btree_write-returned-error.patch

hfsplus-add-error-message-for-the-case-of-failure-of-sync-fs-in-delayed_sync_fs-method.patch
http://ozlabs.org/~akpm/mmots/broken-out/hfsplus-add-error-message-for-the-case-of-failure-of-sync-fs-in-delayed_sync_fs-method.patch


^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [PATCH v2] hfsplus: avoid crash on failed block map free
  2012-12-18 22:47     ` Andrew Morton
@ 2012-12-19  6:26       ` Vyacheslav Dubeyko
  2012-12-19  6:29         ` Andrew Morton
  0 siblings, 1 reply; 13+ messages in thread
From: Vyacheslav Dubeyko @ 2012-12-19  6:26 UTC (permalink / raw)
  To: Andrew Morton; +Cc: Alan Cox, linux-fsdevel, Christoph Hellwig

On Tue, 2012-12-18 at 14:47 -0800, Andrew Morton wrote:
> On Wed, 14 Nov 2012 16:50:53 +0400
> Vyacheslav Dubeyko <slava@dubeyko.com> wrote:
> 
> > On Tue, 2012-11-13 at 14:34 -0800, Andrew Morton wrote:
> > 
> > [snip]
> > > 
> > > The code is missing a flush_dcache_page()?  We should have one in there
> > > after the CPU has modified userspace-mappable page contents.
> > > 
> > 
> > Yes, I think your comment is precious. But I feel a necessity to analyze
> > hfsplus driver code more deeply for proper fix of this issue. An
> > userspace-mappable page content is the main use-case for such fix. But
> > it exists the multi CPUs use-case. So, I need to think about correctness
> > of hfsplus driver for such use-case also, I think.  
> > 
> > > 
> > > 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?
> > > 
> > 
> > So, as you can see the discussion revives again. :-) And I need to
> > familiarize with implementation of xattrs in JFS before to answer again.
> > I had objection that we need to remember about using HFS+ volumes as
> > under Linux as under Mac OS X. Maybe, JFS implementation of xattrs to
> > change my vision.
> 
> I'm still unclear where we stand with these patches.  Which if any of
> these should I merge?
> 

As I can see these patches contain implementation of xattr support (v3)
and reworked error processing in some parts of hfsplus driver. The
version 3 of xattr support was implemented after remarks of Christoph
Hellwig about necessity to have "osx." prefix. So, after this e-mail we
had achieved understanding about proper implementation and it was done.

Maybe I misunderstand something but I thought that these patches were
merged in linux-next yet. Or do you talking about merging in mainline?

Currently, I am working on ACLs support in hfsplus driver. But, from my
point of view, these patches are important and without ACLs support.

With the best regards,
Vyacheslav Dubeyko.

> Thanks.
> 
> hfsplus-avoid-crash-on-failed-block-map-free.patch
> http://ozlabs.org/~akpm/mmots/broken-out/hfsplus-avoid-crash-on-failed-block-map-free.patch
> 
> hfsplus-add-osx-prefix-for-handling-namespace-of-mac-os-x-extended-attributes.patch
> http://ozlabs.org/~akpm/mmots/broken-out/hfsplus-add-osx-prefix-for-handling-namespace-of-mac-os-x-extended-attributes.patch
> 
> hfsplus-add-on-disk-layout-declarations-related-to-attributes-tree.patch
> http://ozlabs.org/~akpm/mmots/broken-out/hfsplus-add-on-disk-layout-declarations-related-to-attributes-tree.patch
> 
> hfsplus-add-functionality-of-manipulating-by-records-in-attributes-tree.patch
> http://ozlabs.org/~akpm/mmots/broken-out/hfsplus-add-functionality-of-manipulating-by-records-in-attributes-tree.patch
> 
> hfsplus-rework-functionality-of-getting-setting-and-deleting-of-extended-attributes.patch
> http://ozlabs.org/~akpm/mmots/broken-out/hfsplus-rework-functionality-of-getting-setting-and-deleting-of-extended-attributes.patch
> 
> hfsplus-add-support-of-manipulation-by-attributes-file.patch
> http://ozlabs.org/~akpm/mmots/broken-out/hfsplus-add-support-of-manipulation-by-attributes-file.patch
> 
> hfsplus-rework-processing-errors-in-hfsplus_free_extents.patch
> http://ozlabs.org/~akpm/mmots/broken-out/hfsplus-rework-processing-errors-in-hfsplus_free_extents.patch
> 
> hfsplus-rework-processing-of-hfs_btree_write-returned-error.patch
> http://ozlabs.org/~akpm/mmots/broken-out/hfsplus-rework-processing-of-hfs_btree_write-returned-error.patch
> 
> hfsplus-add-error-message-for-the-case-of-failure-of-sync-fs-in-delayed_sync_fs-method.patch
> http://ozlabs.org/~akpm/mmots/broken-out/hfsplus-add-error-message-for-the-case-of-failure-of-sync-fs-in-delayed_sync_fs-method.patch
> 



^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [PATCH v2] hfsplus: avoid crash on failed block map free
  2012-12-19  6:26       ` Vyacheslav Dubeyko
@ 2012-12-19  6:29         ` Andrew Morton
  2012-12-19  6:42           ` Vyacheslav Dubeyko
  0 siblings, 1 reply; 13+ messages in thread
From: Andrew Morton @ 2012-12-19  6:29 UTC (permalink / raw)
  To: Vyacheslav Dubeyko; +Cc: Alan Cox, linux-fsdevel, Christoph Hellwig

On Wed, 19 Dec 2012 10:26:37 +0400 Vyacheslav Dubeyko <slava@dubeyko.com> wrote:

> > > So, as you can see the discussion revives again. :-) And I need to
> > > familiarize with implementation of xattrs in JFS before to answer again.
> > > I had objection that we need to remember about using HFS+ volumes as
> > > under Linux as under Mac OS X. Maybe, JFS implementation of xattrs to
> > > change my vision.
> > 
> > I'm still unclear where we stand with these patches.  Which if any of
> > these should I merge?
> > 
> 
> As I can see these patches contain implementation of xattr support (v3)
> and reworked error processing in some parts of hfsplus driver. The
> version 3 of xattr support was implemented after remarks of Christoph
> Hellwig about necessity to have "osx." prefix. So, after this e-mail we
> had achieved understanding about proper implementation and it was done.
> 
> Maybe I misunderstand something but I thought that these patches were
> merged in linux-next yet. Or do you talking about merging in mainline?
> 
> Currently, I am working on ACLs support in hfsplus driver. But, from my
> point of view, these patches are important and without ACLs support.

Yes, they've all been in linux-next for a while.

To be more specific: is Christoph OK with a mainline merge?

^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [PATCH v2] hfsplus: avoid crash on failed block map free
  2012-12-19  6:29         ` Andrew Morton
@ 2012-12-19  6:42           ` Vyacheslav Dubeyko
  2012-12-19 14:09             ` Christoph Hellwig
  0 siblings, 1 reply; 13+ messages in thread
From: Vyacheslav Dubeyko @ 2012-12-19  6:42 UTC (permalink / raw)
  To: Andrew Morton; +Cc: Alan Cox, linux-fsdevel, Christoph Hellwig

On Tue, 2012-12-18 at 22:29 -0800, Andrew Morton wrote:
> On Wed, 19 Dec 2012 10:26:37 +0400 Vyacheslav Dubeyko <slava@dubeyko.com> wrote:
> 
> > > > So, as you can see the discussion revives again. :-) And I need to
> > > > familiarize with implementation of xattrs in JFS before to answer again.
> > > > I had objection that we need to remember about using HFS+ volumes as
> > > > under Linux as under Mac OS X. Maybe, JFS implementation of xattrs to
> > > > change my vision.
> > > 
> > > I'm still unclear where we stand with these patches.  Which if any of
> > > these should I merge?
> > > 
> > 
> > As I can see these patches contain implementation of xattr support (v3)
> > and reworked error processing in some parts of hfsplus driver. The
> > version 3 of xattr support was implemented after remarks of Christoph
> > Hellwig about necessity to have "osx." prefix. So, after this e-mail we
> > had achieved understanding about proper implementation and it was done.
> > 
> > Maybe I misunderstand something but I thought that these patches were
> > merged in linux-next yet. Or do you talking about merging in mainline?
> > 
> > Currently, I am working on ACLs support in hfsplus driver. But, from my
> > point of view, these patches are important and without ACLs support.
> 
> Yes, they've all been in linux-next for a while.
> 
> To be more specific: is Christoph OK with a mainline merge?

I think that we need to ask his about it. :-) I haven't any private
e-mailing with him about it.

Maybe, it makes sense to merge in mainline reworked error processing
patches previously and, then, to merge the xattr support after ACLs
support implementation.

Christoph, could you share your opinion?

With the best regards,
Vyacheslav Dubeyko.

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



^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [PATCH v2] hfsplus: avoid crash on failed block map free
  2012-12-19  6:42           ` Vyacheslav Dubeyko
@ 2012-12-19 14:09             ` Christoph Hellwig
  2012-12-19 14:15               ` Vyacheslav Dubeyko
  0 siblings, 1 reply; 13+ messages in thread
From: Christoph Hellwig @ 2012-12-19 14:09 UTC (permalink / raw)
  To: Vyacheslav Dubeyko
  Cc: Andrew Morton, Alan Cox, linux-fsdevel, Christoph Hellwig

On Wed, Dec 19, 2012 at 10:42:48AM +0400, Vyacheslav Dubeyko wrote:
> > Yes, they've all been in linux-next for a while.
> > 
> > To be more specific: is Christoph OK with a mainline merge?
> 
> I think that we need to ask his about it. :-) I haven't any private
> e-mailing with him about it.
> 
> Maybe, it makes sense to merge in mainline reworked error processing
> patches previously and, then, to merge the xattr support after ACLs
> support implementation.
> 
> Christoph, could you share your opinion?

I haven't actually managed to look at your new xattr patches, but at
least conceptually I'm fine with them.

Let's get the error handling and misc hfsplus patches in ASAP, in the meantime
I'll get a review for the xattr bits in, and then we can decide to merge
them directly or together with the ACL bits.


^ permalink raw reply	[flat|nested] 13+ messages in thread

* Re: [PATCH v2] hfsplus: avoid crash on failed block map free
  2012-12-19 14:09             ` Christoph Hellwig
@ 2012-12-19 14:15               ` Vyacheslav Dubeyko
  0 siblings, 0 replies; 13+ messages in thread
From: Vyacheslav Dubeyko @ 2012-12-19 14:15 UTC (permalink / raw)
  To: Christoph Hellwig; +Cc: Andrew Morton, Alan Cox, linux-fsdevel

On Wed, 2012-12-19 at 15:09 +0100, Christoph Hellwig wrote:
> On Wed, Dec 19, 2012 at 10:42:48AM +0400, Vyacheslav Dubeyko wrote:
> > > Yes, they've all been in linux-next for a while.
> > > 
> > > To be more specific: is Christoph OK with a mainline merge?
> > 
> > I think that we need to ask his about it. :-) I haven't any private
> > e-mailing with him about it.
> > 
> > Maybe, it makes sense to merge in mainline reworked error processing
> > patches previously and, then, to merge the xattr support after ACLs
> > support implementation.
> > 
> > Christoph, could you share your opinion?
> 
> I haven't actually managed to look at your new xattr patches, but at
> least conceptually I'm fine with them.
> 
> Let's get the error handling and misc hfsplus patches in ASAP, in the meantime
> I'll get a review for the xattr bits in, and then we can decide to merge
> them directly or together with the ACL bits.
> 

Ok. Thank you.

With the best regards,
Vyacheslav Dubeyko.

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



^ permalink raw reply	[flat|nested] 13+ messages in thread

end of thread, other threads:[~2012-12-19 14:16 UTC | newest]

Thread overview: 13+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-11-13  9:31 [PATCH v2] hfsplus: avoid crash on failed block map free Vyacheslav Dubeyko
2012-11-13 22:34 ` Andrew Morton
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

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.