From: Joseph Qi <joseph.qi@linux.alibaba.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Gautham Ananthakrishna <gautham.ananthakrishna@oracle.com>
Cc: junxiao.bi@oracle.com, rajesh.sivaramasubramaniom@oracle.com,
ocfs2-devel@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC V4 1/1] ocfs2: reserve space for inline xattr before attaching reflink tree
Date: Wed, 18 Sep 2024 09:57:05 +0800 [thread overview]
Message-ID: <a4ff61ae-c83d-4a6d-837a-4e3c22c99a69@linux.alibaba.com> (raw)
In-Reply-To: <20240916091647.dbcca9d29f081c7a4c5cd2ea@linux-foundation.org>
On 9/17/24 12:16 AM, Andrew Morton wrote:
> On Thu, 12 Sep 2024 06:47:20 +0000 Gautham Ananthakrishna <gautham.ananthakrishna@oracle.com> wrote:
>
>> One of our customers reported a crash and a corrupted ocfs2 filesystem.
>> +++ b/fs/ocfs2/refcounttree.c
>> @@ -25,6 +25,7 @@
>> #include "namei.h"
>> #include "ocfs2_trace.h"
>> #include "file.h"
>> +#include "symlink.h"
>>
>> #include <linux/bio.h>
>> #include <linux/blkdev.h>
>> @@ -4155,8 +4156,9 @@ static int __ocfs2_reflink(struct dentry *old_dentry,
>> int ret;
>> struct inode *inode = d_inode(old_dentry);
>> struct buffer_head *new_bh = NULL;
>> + struct ocfs2_inode_info *oi = OCFS2_I(inode);
>>
>> - if (OCFS2_I(inode)->ip_flags & OCFS2_INODE_SYSTEM_FILE) {
>> + if (oi->ip_flags & OCFS2_INODE_SYSTEM_FILE) {
>> ret = -EINVAL;
>> mlog_errno(ret);
>> goto out;
>> @@ -4182,6 +4184,26 @@ static int __ocfs2_reflink(struct dentry *old_dentry,
>> goto out_unlock;
>> }
>>
>> + if ((oi->ip_dyn_features & OCFS2_HAS_XATTR_FL) &&
>> + (oi->ip_dyn_features & OCFS2_INLINE_XATTR_FL)) {
>> + /*
>> + * Adjust extent record count to reserve space for extended attribute.
>> + * Inline data count had been adjusted in ocfs2_duplicate_inline_data().
>> + */
>> + struct ocfs2_inode_info *new_oi = OCFS2_I(new_inode);
>> +
>> + if (!(new_oi->ip_dyn_features & OCFS2_INLINE_DATA_FL) &&
>> + !(ocfs2_inode_is_fast_symlink(new_inode))) {
>> + struct ocfs2_dinode *new_di = new_bh->b_data;
>> + struct ocfs2_dinode *old_di = old_bh->b_data;
>
> fs/ocfs2/refcounttree.c: In function '__ocfs2_reflink':
> fs/ocfs2/refcounttree.c:4190:55: error: initialization of 'struct ocfs2_dinode *' from incompatible pointer type 'char *' [-Werror=incompatible-pointer-types]
> 4190 | struct ocfs2_dinode *new_di = new_bh->b_data;
> | ^~~~~~
> fs/ocfs2/refcounttree.c:4191:55: error: initialization of 'struct ocfs2_dinode *' from incompatible pointer type 'char *' [-Werror=incompatible-pointer-types]
> 4191 | struct ocfs2_dinode *old_di = old_bh->b_data;
> | ^~~~~~
> cc1: all warnings being treated as errors
>
> I could just add the typecasts, but that doesn't give me a tested patch :(
>
Oops, sorry for missing this when reviewing.
Hi Gautham, could you please add the missing typecasts and confirm it?
Thanks,
Joseph
next prev parent reply other threads:[~2024-09-18 1:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 6:47 Gautham Ananthakrishna
2024-09-16 16:16 ` Andrew Morton
2024-09-18 1:57 ` Joseph Qi [this message]
2024-09-18 6:40 ` Gautham Ananthakrishna
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=a4ff61ae-c83d-4a6d-837a-4e3c22c99a69@linux.alibaba.com \
--to=joseph.qi@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=gautham.ananthakrishna@oracle.com \
--cc=junxiao.bi@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ocfs2-devel@lists.linux.dev \
--cc=rajesh.sivaramasubramaniom@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
all inboxes | Powered by JetHome®