debugfs: dump a sparse file as a new sparse file
Status from this message: Thanks, applied. I did make one change to the above line:
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 Latest2 patches 8 repliesApplied
- v11 patch 6 repliesSuperseded
Patches in v2 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | debugfs: fixup the hard-coded buffer length in dump_filedebugfs/ | +10 | 1 reply | |
| 2/2 | debugfs: dump a sparse file as a new sparse filedebugfs/ lib/ lib/ | +55 | 7 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.
Cover letter [PATCH 0/2 v2] debugfs: dump a sparse file as a new sparse file
Currently when we use dump command in debugfs to dump a file, all extents will be dumped to a new file no matter whether these extents are written or not. If we want to dump a sparse file, it will waste time to fill zero into the file. This patch series tries to avoid to dump unwritten extent.
v2 <- v1:
- split original patch into two parts.
- make code clearly according to Ted's suggestions
Here is the first version:
http://patchwork.ozlabs.org/patch/199303/
Regards,
- Zheng
Zheng Liu (2):
debugfs: fixup the hard-coded buffer length in dump_file
debugfs: dump a sparse file as a new sparse file
debugfs/dump.c | 25 ++++++++++++++++++++++--- lib/ext2fs/ext2fs.h | 3 +++ lib/ext2fs/fileio.c | 50 +++++++++++++++++++++++++++++++++++++++----------- 3 files changed, 64 insertions(+), 14 deletions(-)
Signature · 1 line
1.7.12.rc2.18.g61b472e