From: Mingming Cao <cmm@us.ibm.com>
To: Akira Fujita <a-fujita@rs.jp.nec.com>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
Andreas Dilger <adilger@sun.com>,
tytso@mit.edu, linux-ext4@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/5] ext4 online defrag header file changes
Date: Fri, 28 Mar 2008 17:49:43 -0700 [thread overview]
Message-ID: <1206751783.3629.17.camel@localhost.localdomain> (raw)
In-Reply-To: <47EB73DE.7050702@rs.jp.nec.com>
On Thu, 2008-03-27 at 19:15 +0900, Akira Fujita wrote:
> Aneesh Kumar K.V wrote:
> > On Mon, Mar 24, 2008 at 09:31:03PM +0900, Akira Fujita wrote:
> >
> >> Hi Aneesh,
> >>
> >>> On Mon, Mar 24, 2008 at 08:00:54PM +0900, Akira Fujita wrote:
> >>>
> >>>>>
> >>>>>
> >>>> Is EXT4_IOC_FIEMAP going to be added to the ext4 patch queue?
> >>>> I will try to use EXT4_IOC_FIEMAP instead of EXT4_IOC_EXTENTS_INFO
> >>>> in ext4 online defrag when kernel supports it.
> >>>>
> >>> Can you also look at the sparse warnings with the patches ?
> >>>
> >>>
> >> I have already released the fixed patch before, but it is not in the ext4 patch queue yet.
> >> Mingming, could you replace new ext4-online-defrag-free-space-fragmentation.patch
> >> with old one in the ext4 patch queue?
> >>
> >>
> >
> > CHECK fs/ext4/defrag.c
> > fs/ext4/defrag.c:181:7: warning: cast to restricted type
> > fs/ext4/defrag.c:181:7: warning: cast from restricted type
> > fs/ext4/defrag.c:613:21: warning: incorrect type in argument 1
> > (different address spaces)
> > fs/ext4/defrag.c:613:21: expected void [noderef] <asn:1>*to
> > fs/ext4/defrag.c:613:21: got struct ext4_group_data_info *<noident>
> > fs/ext4/defrag.c:629:24: warning: incorrect type in argument 1
> > (different address spaces)
> > fs/ext4/defrag.c:629:24: expected void [noderef] <asn:1>*to
> > fs/ext4/defrag.c:629:24: got struct ext4_extents_info *<noident>
> > fs/ext4/defrag.c:849:29: warning: potentially expensive pointer
> > subtraction
> > fs/ext4/defrag.c:912:22: warning: potentially expensive pointer
> > subtraction
> >
> > you would need http://www.kernel.org/pub/software/devel/sparse/
> > to find and fix these warnings.
> >
> >
> Oops, there are a lot of warnings. =-O
> Thank you for letting me know.
> I will release fixed defrag patches in a few days.
As part of transition to move ext4 related header files out of
include/linux, and move to fs/ext4, I also updated the defrag patches to
adapt this change. You might want to checkout the defrag patches in
patch queue and merge the updates before release the new version.
Cheers,
Mingming
next prev parent reply other threads:[~2008-03-29 0:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-24 12:31 [PATCH 1/5] ext4 online defrag header file changes Akira Fujita
2008-03-25 17:48 ` Aneesh Kumar K.V
2008-03-27 10:15 ` Akira Fujita
2008-03-29 0:49 ` Mingming Cao [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-03-31 8:46 Akira Fujita
2008-03-24 12:34 Akira Fujita
2008-03-14 12:02 Akira Fujita
2008-03-14 12:58 ` Andreas Dilger
2008-03-17 6:28 ` Akira Fujita
2008-03-17 17:08 ` Andreas Dilger
2008-03-24 11:00 ` Akira Fujita
2008-03-24 11:16 ` Aneesh Kumar K.V
2008-03-24 15:00 ` Eric Sandeen
2008-03-25 2:21 ` Akira Fujita
[not found] <1204931337.14884.43.camel@localhost.localdomain>
2008-03-08 0:18 ` Mingming Cao
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=1206751783.3629.17.camel@localhost.localdomain \
--to=cmm@us.ibm.com \
--cc=a-fujita@rs.jp.nec.com \
--cc=adilger@sun.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=tytso@mit.edu \
/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).