Linux ocfs2 filesystem development
 help / color / mirror / Atom feed
From: Joseph Qi <joseph.qi@huawei.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] Patch for reviews, thanks
Date: Wed, 24 Feb 2016 09:53:36 +0800	[thread overview]
Message-ID: <56CD0D20.5020809@huawei.com> (raw)
In-Reply-To: <71604351584F6A4EBAE558C676F37CA482934320@H3CMLB14-EX.srv.huawei-3com.com>

Hi Guozhonghua,
Thanks for pointing this out.
But you should follow the way described in
Documentation/SubmittingPatches to submit your patch.
I'll re-arrange and resend it.

Thanks,
Joseph

On 2016/2/24 9:11, Guozhonghua wrote:
> 
> aops.c, in the function ocfs2_direct_IO_write.
> 
> *************** clean_orphan:
> *** 948,961 ****
> --- 947,963 ----
>                 tmp_ret = ocfs2_inode_lock(inode, &di_bh, 1);
>                 if (tmp_ret < 0) {
>                         ret = tmp_ret;
>                         mlog_errno(ret);
>                         goto out;
>                 }
> 
>                 tmp_ret = ocfs2_del_inode_from_orphan(osb, inode, di_bh,
>                                 update_isize, end);
>                 if (tmp_ret < 0) {
>                         ret = tmp_ret;
>                         mlog_errno(ret);
> +                       ocfs2_inode_unlock(inode, 1);
>                         brelse(di_bh);
>                         goto out;
>                 }
> 
>                 ocfs2_inode_unlock(inode, 1);
>                 brelse(di_bh);
> -------------------------------------------------------------------------------------------------------------------------------------
> ????????????????????????????????????????
> ????????????????????????????????????????
> ????????????????????????????????????????
> ???
> This e-mail and its attachments contain confidential information from H3C, which is
> intended only for the person or entity whose address is listed above. Any use of the
> information contained herein in any way (including, but not limited to, total or partial
> disclosure, reproduction, or dissemination) by persons other than the intended
> recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender
> by phone or email immediately and delete it!
> _______________________________________________
> Ocfs2-devel mailing list
> Ocfs2-devel at oss.oracle.com
> https://oss.oracle.com/mailman/listinfo/ocfs2-devel
> 

      reply	other threads:[~2016-02-24  1:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-24  1:11 [Ocfs2-devel] Patch for reviews, thanks Guozhonghua
2016-02-24  1:53 ` Joseph Qi [this message]

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=56CD0D20.5020809@huawei.com \
    --to=joseph.qi@huawei.com \
    --cc=ocfs2-devel@oss.oracle.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