From: ChenXiaoSong <chenxiaosong2@huawei.com>
To: Viacheslav Dubeyko <slava@dubeyko.com>
Cc: Bart Van Assche <bvanassche@acm.org>,
Andrew Morton <akpm@linux-foundation.org>,
Aditya Garg <gargaditya08@live.com>, Jens Axboe <axboe@kernel.dk>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Damien Le Moal <damien.lemoal@opensource.wdc.com>,
Jeff Layton <jlayton@kernel.org>, <hannes@cmpxchg.org>,
"Theodore Y . Ts'o" <tytso@mit.edu>, <muchun.song@linux.dev>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] hfsplus: fix uninit-value in hfsplus_delete_cat()
Date: Fri, 16 Dec 2022 09:16:29 +0800 [thread overview]
Message-ID: <946950be-482c-ef9f-404c-2ce758ba175d@huawei.com> (raw)
In-Reply-To: <6258B9FC-0A00-46BC-9C6C-720963D58A06@dubeyko.com>
在 2022/12/16 3:03, Viacheslav Dubeyko 写道:
>
> Maybe, I am missing something. But where in the second version of the patch
> initialization of subfolders?
>
The first patch of the patchset factor out hfsplus_init_inode() from
hfsplus_new_inode():
void hfsplus_init_inode(struct hfsplus_inode_info *hip)
{
INIT_LIST_HEAD(&hip->open_dir_list);
spin_lock_init(&hip->open_dir_lock);
mutex_init(&hip->extents_lock);
atomic_set(&hip->opencnt, 0);
hip->extent_state = 0;
hip->flags = 0;
hip->userflags = 0;
hip->subfolders = 0; /* I am here */
memset(hip->first_extents, 0, sizeof(hfsplus_extent_rec));
memset(hip->cached_extents, 0, sizeof(hfsplus_extent_rec));
hip->alloc_blocks = 0;
hip->first_blocks = 0;
hip->cached_start = 0;
hip->cached_blocks = 0;
hip->phys_size = 0;
hip->fs_blocks = 0;
hip->rsrc_inode = NULL;
}
next prev parent reply other threads:[~2022-12-16 1:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 8:18 [PATCH v2 0/2] initialize 'struct hfsplus_inode_info' in hfsplus_iget() ChenXiaoSong
2022-12-15 8:18 ` [PATCH v2 1/2] hfsplus: introduce hfsplus_init_inode() helper ChenXiaoSong
2022-12-15 8:18 ` [PATCH v2 2/2] hfsplus: fix uninit-value in hfsplus_delete_cat() ChenXiaoSong
2022-12-15 19:03 ` Viacheslav Dubeyko
2022-12-16 1:16 ` ChenXiaoSong [this message]
2022-12-16 18:09 ` Viacheslav Dubeyko
2022-12-17 2:20 ` ChenXiaoSong
2023-01-13 3:43 ` [PATCH v2 0/2] initialize 'struct hfsplus_inode_info' in hfsplus_iget() ChenXiaoSong
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=946950be-482c-ef9f-404c-2ce758ba175d@huawei.com \
--to=chenxiaosong2@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=damien.lemoal@opensource.wdc.com \
--cc=gargaditya08@live.com \
--cc=hannes@cmpxchg.org \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=muchun.song@linux.dev \
--cc=slava@dubeyko.com \
--cc=tytso@mit.edu \
--cc=willy@infradead.org \
/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®