From: Daeho Jeong <daeho.jeong@samsung.com>
To: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Cc: "daehojng@gmail.com" <daehojng@gmail.com>, 정대호 <daeho.jeong@samsung.com>
Subject: A question about EXT4_INODE_JOURNAL_DATA flag with delalloc
Date: Tue, 11 Aug 2015 03:12:56 +0000 (GMT) [thread overview]
Message-ID: <854180411.692591439262776858.JavaMail.weblogic@epmlwas07d> (raw)
Hi, I am seeing in the ext4_change_inode_flag() function and found a patch to allocate
physical blocks for delalloc blocks in that function.
(=> http://repo.or.cz/w/ext4-patch-queue.git/blob/20f7782b1f50eb1d5cba5e085d01fbce89fce881:/allocate-delalloc-blocks-before-changing-journal-mode)
I think this is an idea to resolve kernel OOPS concerned with enabling/disabling
data journaling of a file in delayed allocation mode. Actually, I want to utilize per file
data journaling with delayed allocation, so this patch seemed to be very helpful for me.
But, after 1 month from when the patch was applied, another patch was submitted
and EXT4_INODE_JOURNAL_DATA flag with delalloc was ignored.
(=> http://repo.or.cz/w/ext4-patch-queue.git/blob/17f3a9c17473d0b5925118a75ba7363c79e3fdc3:/ignore-JOURNAL_DATA-flag-with-delalloc)
I don't understand the reason of that EXT4_INODE_JOURNAL_DATA flag with delalloc was
ignored because I think the previous patch can handle the problem which the above URL describes.
Am I missing something and could you share your idea about this? :-)
next reply other threads:[~2015-08-11 3:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 3:12 Daeho Jeong [this message]
2015-08-11 20:00 ` A question about EXT4_INODE_JOURNAL_DATA flag with delalloc Theodore Ts'o
-- strict thread matches above, loose matches on Subject: below --
2015-08-12 6:07 Daeho Jeong
2015-08-12 15:31 ` Theodore Ts'o
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=854180411.692591439262776858.JavaMail.weblogic@epmlwas07d \
--to=daeho.jeong@samsung.com \
--cc=daehojng@gmail.com \
--cc=linux-ext4@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).