All of lore.kernel.org
 help / color / mirror / Atom feed
From: Akira Fujita <a-fujita@rs.jp.nec.com>
To: Derkjan de Haan <haanjdj@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Fwd: can't get e4defrag to work
Date: Tue, 03 Feb 2009 17:02:52 +0900	[thread overview]
Message-ID: <4987FA2C.7090700@rs.jp.nec.com> (raw)
In-Reply-To: <7a45233b0901301307t5f045ddflc9fdbeb48bbcad0@mail.gmail.com>

Hi Derkjan,

Derkjan de Haan wrote:
> I would like to report the following issues:
> 
> - the patch doesn't apply cleanly to 2.6.29-rc3:
> 
> Applying patch patches/1
> patching file fs/ext4/Makefile
> patching file fs/ext4/defrag.c
> patching file fs/ext4/ext4.h
> Hunk #1 succeeded at 303 (offset 10 lines).
> Hunk #2 succeeded at 312 with fuzz 2 (offset -2 lines).
> Hunk #3 succeeded at 1033 (offset 9 lines).
> patching file fs/ext4/ext4_extents.h
> patching file fs/ext4/extents.c
> patching file fs/ext4/ioctl.c
> Hunk #2 succeeded at 215 (offset -11 lines).
> 
> Applying patch patches/2
> patching file fs/ext4/defrag.c
> 
> Now at patch patches/2

Defrag pathces applied cleanly to the ext4 patch queue
(7554f240866634a3b5394aced79e1768b4b1f3bf) without any hunks.

[root@bsd086 KERN]# patch -d linux-2.6.29-rc3 -p1 < 1.patch
patching file fs/ext4/Makefile
patching file fs/ext4/defrag.c
patching file fs/ext4/ext4.h
patching file fs/ext4/ext4_extents.h
patching file fs/ext4/extents.c
patching file fs/ext4/ioctl.c

Maybe your ext4 patch queue was not the latest version.

> 
> - I just found out e4defrag needs to be compiled with the -lm flag due
> to the powf function being used.

Yes.  I should have mentioned it in advance.

> - When compiling ext4 as a module, the kernel build fails on this error:
> 
> ERROR: "fget_light" [fs/ext4/ext4.ko] undefined!
> make[1]: *** [__modpost] Error 1
> make: *** [modules] Error 2
> 

Thank you for reporting.
I will use fget() and fput() in the next version instead.

Regards,
Akira Fujita

  reply	other threads:[~2009-02-03  8:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7a45233b0901210704w5038d8b8g5c657e3a4746f34d@mail.gmail.com>
2009-01-23  7:23 ` can't get e4defrag to work Akira Fujita
2009-01-23 15:51   ` Greg Freemyer
2009-01-26  7:37     ` Akira Fujita
2009-01-26 12:09       ` Sandeep K Sinha
2009-01-30 13:07         ` Derkjan de Haan
2009-01-30 21:07           ` Fwd: " Derkjan de Haan
2009-02-03  8:02             ` Akira Fujita [this message]
2009-01-23 19:08   ` Derkjan de Haan
2009-01-26  7:41     ` Akira Fujita

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=4987FA2C.7090700@rs.jp.nec.com \
    --to=a-fujita@rs.jp.nec.com \
    --cc=haanjdj@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 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.