From: sunny.s.zhang <sunny.s.zhang@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2: fix ocfs2 read inode data panic in ocfs2_iget
Date: Fri, 29 Mar 2019 11:24:27 +0800 [thread overview]
Message-ID: <1d449c4e-d4e0-88bb-4288-e53e925c8226@oracle.com> (raw)
In-Reply-To: <f4a83860-8e81-3a2e-66e0-bebc0c8e3426@gmail.com>
Hi Joseph,
? 2019?03?29? 10:21, Joseph Qi ??:
>
> On 19/3/29 09:05, sunny.s.zhang wrote:
>> Hi Gang,? Jiang Qi,? Joseph,
>>
>> Is my description clear?
>> Are there any other suggestions?
>> In addition, it works fine on ext4.
> So this happens when using ocfs2 as NFSv3 backend, right?
> If so, please describe the use case in commit log as well as the
> sequence how it happens.
Thank you very much for the feedback.
OK, I will add it to the commit log.
>
> BTW, since the dinode has been deleted, the block may be used in other
> way. So I don't think we can use "di->i_dtime != 0" to identify this
> case.
Yes, Although the time window is very small, it is strictly possible to
happen.
I will make a new patch and consider the above question.
Thanks,
Sunny
>
> Thanks,
> Joseph
next prev parent reply other threads:[~2019-03-29 3:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 1:26 [Ocfs2-devel] [PATCH] ocfs2: fix ocfs2 read inode data panic in ocfs2_iget Shuning Zhang
2019-03-25 1:31 ` Joseph Qi
2019-03-25 1:32 ` piaojun
2019-03-25 2:18 ` sunny.s.zhang
2019-03-25 3:11 ` Gang He
2019-03-25 6:15 ` sunny.s.zhang
2019-03-29 1:05 ` sunny.s.zhang
2019-03-29 2:21 ` Joseph Qi
2019-03-29 3:24 ` sunny.s.zhang [this message]
2019-03-29 4:31 ` Gang He
2019-03-29 4:43 ` sunny.s.zhang
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=1d449c4e-d4e0-88bb-4288-e53e925c8226@oracle.com \
--to=sunny.s.zhang@oracle.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.