linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vyacheslav Dubeyko <slava@dubeyko.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org,
	Christoph Hellwig <hch@infradead.org>,
	Al Viro <viro@zeniv.linux.org.uk>,
	Hin-Tak Leung <htl10@users.sourceforge.net>
Subject: Re: [PATCH v2 2/4] hfsplus: add functionality of manipulating by records in attributes tree
Date: Tue, 25 Sep 2012 10:20:13 +0400	[thread overview]
Message-ID: <1348554013.2033.26.camel@slavad-ubuntu-11> (raw)
In-Reply-To: <20120924154913.0afbc1e3.akpm@linux-foundation.org>

Hi,

Ok. I agree with all your remarks. I will correct it.

Do I need prepare a new version of patch set or simply patch for these
corrections?

With the best regards,
Vyacheslav Dubeyko.

On Mon, 2012-09-24 at 15:49 -0700, Andrew Morton wrote:
> On Sun, 23 Sep 2012 18:49:24 +0400
> Vyacheslav Dubeyko <slava@dubeyko.com> wrote:
> 
> > This patch adds functionality of manipulating by records in attributes tree.
> 
> Some minor things:
> 
> >
> > ...
> >
> > +int hfsplus_attr_build_key(struct super_block *sb, hfsplus_btree_key *key,
> > +			u32 cnid, const char *name)
> > +{
> > +	int len;
> > +
> > +	memset(key, 0, sizeof(struct hfsplus_attr_key));
> > +	key->attr.cnid = cpu_to_be32(cnid);
> > +	if (name) {
> > +		len = strlen(name);
> > +		if (len > HFSPLUS_ATTR_MAX_STRLEN) {
> > +			printk(KERN_ERR "hfs: invalid xattr name's length\n");
> > +			return -EINVAL;
> > +		}
> > +		hfsplus_asc2uni(sb,
> > +				(struct hfsplus_unistr *)&key->attr.key_name,
> > +				HFSPLUS_ATTR_MAX_STRLEN, name, len);
> > +		len = be16_to_cpu(key->attr.key_name.length);
> > +	} else {
> > +		key->attr.key_name.length = 0;
> > +		len = 0;
> > +	}
> > +	/* The key_length (be16) doesn't summed in the lenght of whole key.
> 
> s/lenght/length/
> 
> Also, this sentence is rather hard to understand.  Rephrase, please?
> 
> > +	   But the length of the string (be16) should be included in sum.
> > +	   So, offsetof(hfsplus_attr_key, key_name) is a trick that give
> > +	   right value. */
> 
> The usual layout style for multiline comments is
> 
> 	/*
> 	 * ...
> 	 * ...
> 	 */
> 
> > +	key->key_len =
> > +		cpu_to_be16(offsetof(struct hfsplus_attr_key, key_name) +
> > +				2 * len);
> > +
> > +	return 0;
> > +}
> > +
> > +void hfsplus_attr_build_key_uni(hfsplus_btree_key *key,
> > +					u32 cnid,
> > +					struct hfsplus_attr_unistr *name)
> > +{
> > +	int ustrlen;
> > +
> > +	memset(key, 0, sizeof(struct hfsplus_attr_key));
> > +	ustrlen = be16_to_cpu(name->length);
> > +	key->attr.cnid = cpu_to_be32(cnid);
> > +	key->attr.key_name.length = cpu_to_be16(ustrlen);
> > +	ustrlen *= 2;
> > +	memcpy(key->attr.key_name.unicode, name->unicode, ustrlen);
> > +	/* The key_length (be16) doesn't summed in the lenght of whole key.
> > +	   But the length of the string (be16) should be included in sum.
> > +	   So, offsetof(hfsplus_attr_key, key_name) is a trick that give
> > +	   right value. */
> 
> dittoes.
> 
> > +	key->key_len =
> > +		cpu_to_be16(offsetof(struct hfsplus_attr_key, key_name) +
> > +				ustrlen);
> > +}
> > +
> > +hfsplus_attr_entry *hfsplus_alloc_attr_entry(void)
> > +{
> > +	hfsplus_attr_entry *entry;
> > +	entry = kmem_cache_alloc(hfsplus_attr_tree_cachep, GFP_KERNEL);
> > +
> > +	return (entry) ? entry : NULL;
> > +}
> 
> This is rather verbose.  It could be
> 
> hfsplus_attr_entry *hfsplus_alloc_attr_entry(void)
> {
> 	return kmem_cache_alloc(hfsplus_attr_tree_cachep, GFP_KERNEL);
> }
> 
> >
> > ...
> >
> 



  reply	other threads:[~2012-09-25  6:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-23 14:49 [PATCH v2 2/4] hfsplus: add functionality of manipulating by records in attributes tree Vyacheslav Dubeyko
2012-09-24 22:49 ` Andrew Morton
2012-09-25  6:20   ` Vyacheslav Dubeyko [this message]
2012-09-25  8:26     ` Andrew Morton

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=1348554013.2033.26.camel@slavad-ubuntu-11 \
    --to=slava@dubeyko.com \
    --cc=akpm@linux-foundation.org \
    --cc=hch@infradead.org \
    --cc=htl10@users.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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).