All of lore.kernel.org
 help / color / mirror / Atom feed
From: shencanquan <shencanquan@huawei.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2_prep_new_orphaned_file should return ret
Date: Wed, 22 May 2013 10:44:51 +0800	[thread overview]
Message-ID: <519C3123.6070908@huawei.com> (raw)
In-Reply-To: <519C2F93.3070408@oracle.com>

On 2013/5/22 10:38, xiaowei.hu wrote:
> if there is error happen in , for example EIO in 
> __ocfs2_prepare_orphan_dir, ocfs2_prep_new_orphaned_file will release 
> the inode_ac, the the caller of ocfs2_prep_new_orphaned_file get a 0 
> return, it will refer to a NULL ocfs2_alloc_context struct in the 
> following functions.Kernel panic happens.
Hmm, I see, this patch looks good .
Reviewed-by: shencanquan <shencanquan@huawei.com>
>
> On 05/22/2013 10:31 AM, shencanquan wrote:
>> if return 0,  what's wrong with this?
>> On 2013/5/22 9:43, xiaowei.hu at oracle.com wrote:
>>> From: "Xiaowei.Hu"<xiaowei.hu@oracle.com>
>>>
>>> ---
>>>   fs/ocfs2/namei.c | 2 +-
>>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/fs/ocfs2/namei.c b/fs/ocfs2/namei.c
>>> index 50c93a8..422cbe0 100644
>>> --- a/fs/ocfs2/namei.c
>>> +++ b/fs/ocfs2/namei.c
>>> @@ -2216,7 +2216,7 @@ out:
>>>
>>>       brelse(orphan_dir_bh);
>>>
>>> -    return 0;
>>> +    return ret;
>>>   }
>>>
>>>   int ocfs2_create_inode_in_orphan(struct inode *dir,
>>
>>
>
>
>

  reply	other threads:[~2013-05-22  2:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-22  1:43 [Ocfs2-devel] [PATCH] ocfs2_prep_new_orphaned_file should return ret xiaowei.hu at oracle.com
2013-05-22  2:31 ` shencanquan
2013-05-22  2:38   ` xiaowei.hu
2013-05-22  2:44     ` shencanquan [this message]
2013-05-22 22:50       ` Sunil Mushran
2013-05-27  5:28         ` Joe Jin
2013-05-28 22:35 ` Andrew Morton
2013-05-29  1:06   ` xiaowei.hu

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=519C3123.6070908@huawei.com \
    --to=shencanquan@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 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.