Re: NILFS 2.0.19 and NILFS utils 2.0.16 released
Hi, At Sat, 13 Mar 2010 15:06:12 +0900 (JST), Ryusuke Konishi wrote: Hi, I have released nilfs-2.0.19 and nilfs-utils-2.0.16. I found that COPYING of nilfs-utils is now GPL v3. I've checked older version. Until 2.0.14, it was GPL v2, however it upgraded to v3 in 2.0.15. It looks like there is no COPYING file in the git repository. Therefore, I guess, it was automatically copied by automake when creating tarball. Or is it indented to be GPL v3 now? thanks regards, nilfs-2.0.19 is the latest standalone module maintained for older kernels. This release backported several bug fixes and some problem-solving updates from the mainline kernel; the following changes are included: * fix potential hang in nilfs_error on errors=remount-ro * add missing reader's lock in nilfs_ioctl_sync * fix potential leak of dirty data on umount * show missing mount options in /proc/mounts. * change mount option to disable write barriers; nobarrier is used instead of barrier=off. * add norecovery mount option * use mnt_want_write in ioctls where write access is needed * apply readahead for recovery on mount * sync superblock by nilfs thread instead of periodic write_super callback * update mailing list address * coding style fixes The changes of nilfs-utils include manpage updates, a build fix for newer glibc, and a mount option to set protection_period. The updated packages are available at http://www.nilfs.org/en/download.html Thanks, Ryusuke Konishi -- To unsubscribe from this list: send the line unsubscribe linux-nilfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- Jiro SEKIBA j...@unicus.jp -- To unsubscribe from this list: send the line unsubscribe linux-nilfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: NILFS 2.0.19 and NILFS utils 2.0.16 released
On Sat, 13 Mar 2010 17:04:13 +0900, Jiro SEKIBA wrote: Hi, At Sat, 13 Mar 2010 15:06:12 +0900 (JST), Ryusuke Konishi wrote: Hi, I have released nilfs-2.0.19 and nilfs-utils-2.0.16. I found that COPYING of nilfs-utils is now GPL v3. I've checked older version. Until 2.0.14, it was GPL v2, however it upgraded to v3 in 2.0.15. It looks like there is no COPYING file in the git repository. Therefore, I guess, it was automatically copied by automake when creating tarball. Or is it indented to be GPL v3 now? Ahhh, that is an accident. Ok, I will add a COPYING file to resolve this problem. Thank you for letting me know! Ryusuke Konishi thanks regards, nilfs-2.0.19 is the latest standalone module maintained for older kernels. This release backported several bug fixes and some problem-solving updates from the mainline kernel; the following changes are included: * fix potential hang in nilfs_error on errors=remount-ro * add missing reader's lock in nilfs_ioctl_sync * fix potential leak of dirty data on umount * show missing mount options in /proc/mounts. * change mount option to disable write barriers; nobarrier is used instead of barrier=off. * add norecovery mount option * use mnt_want_write in ioctls where write access is needed * apply readahead for recovery on mount * sync superblock by nilfs thread instead of periodic write_super callback * update mailing list address * coding style fixes The changes of nilfs-utils include manpage updates, a build fix for newer glibc, and a mount option to set protection_period. The updated packages are available at http://www.nilfs.org/en/download.html Thanks, Ryusuke Konishi -- To unsubscribe from this list: send the line unsubscribe linux-nilfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- Jiro SEKIBA j...@unicus.jp -- To unsubscribe from this list: send the line unsubscribe linux-nilfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line unsubscribe linux-nilfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: NILFS 2.0.19 and NILFS utils 2.0.16 released
2010/3/13 Ryusuke Konishi ryus...@osrg.net: On Sat, 13 Mar 2010 17:04:13 +0900, Jiro SEKIBA wrote: Hi, At Sat, 13 Mar 2010 15:06:12 +0900 (JST), Ryusuke Konishi wrote: Hi, I have released nilfs-2.0.19 and nilfs-utils-2.0.16. I found that COPYING of nilfs-utils is now GPL v3. I've checked older version. Until 2.0.14, it was GPL v2, however it upgraded to v3 in 2.0.15. It looks like there is no COPYING file in the git repository. Therefore, I guess, it was automatically copied by automake when creating tarball. Or is it indented to be GPL v3 now? Ahhh, that is an accident. Ok, I will add a COPYING file to resolve this problem. Done. I made another util release (nilfs-utils-2.0.17). Ryusuke Konishi -- To unsubscribe from this list: send the line unsubscribe linux-nilfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[PATCH 4/6] nilfs2: fix various typos in comments
This fixes various typos I found in comments of nilfs2.
Signed-off-by: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
---
fs/nilfs2/alloc.h |2 +-
fs/nilfs2/dat.c |2 +-
fs/nilfs2/gcinode.c |4 ++--
fs/nilfs2/page.c|4 ++--
fs/nilfs2/segbuf.c |2 +-
fs/nilfs2/segment.c |4 ++--
fs/nilfs2/segment.h |2 +-
fs/nilfs2/sufile.c |2 +-
fs/nilfs2/super.c |2 +-
9 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/fs/nilfs2/alloc.h b/fs/nilfs2/alloc.h
index f4543ac..5cccf87 100644
--- a/fs/nilfs2/alloc.h
+++ b/fs/nilfs2/alloc.h
@@ -42,7 +42,7 @@ void *nilfs_palloc_block_get_entry(const struct inode *,
__u64,
const struct buffer_head *, void *);
/**
- * nilfs_palloc_req - persistent alloctor request and reply
+ * nilfs_palloc_req - persistent allocator request and reply
* @pr_entry_nr: entry number (vblocknr or inode number)
* @pr_desc_bh: buffer head of the buffer containing block group descriptors
* @pr_bitmap_bh: buffer head of the buffer containing a block group bitmap
diff --git a/fs/nilfs2/dat.c b/fs/nilfs2/dat.c
index 9d1e5de..0131467 100644
--- a/fs/nilfs2/dat.c
+++ b/fs/nilfs2/dat.c
@@ -288,7 +288,7 @@ int nilfs_dat_mark_dirty(struct inode *dat, __u64 vblocknr)
* @vblocknrs and @nitems.
*
* Return Value: On success, 0 is returned. On error, one of the following
- * nagative error codes is returned.
+ * negative error codes is returned.
*
* %-EIO - I/O error.
*
diff --git a/fs/nilfs2/gcinode.c b/fs/nilfs2/gcinode.c
index e16a666..8880a9e 100644
--- a/fs/nilfs2/gcinode.c
+++ b/fs/nilfs2/gcinode.c
@@ -28,10 +28,10 @@
* gcinodes), and this file provides lookup function of the dummy
* inodes and their buffer read function.
*
- * Since NILFS2 keeps up multiple checkpoints/snapshots accross GC, it
+ * Since NILFS2 keeps up multiple checkpoints/snapshots across GC, it
* has to treat blocks that belong to a same file but have different
* checkpoint numbers. To avoid interference among generations, dummy
- * inodes are managed separatly from actual inodes, and their lookup
+ * inodes are managed separately from actual inodes, and their lookup
* function (nilfs_gc_iget) is designed to be specified with a
* checkpoint number argument as well as an inode number.
*
diff --git a/fs/nilfs2/page.c b/fs/nilfs2/page.c
index a2692bb..fc246db 100644
--- a/fs/nilfs2/page.c
+++ b/fs/nilfs2/page.c
@@ -292,7 +292,7 @@ void nilfs_free_private_page(struct page *page)
* @src: source page
* @copy_dirty: flag whether to copy dirty states on the page's buffer heads.
*
- * This fuction is for both data pages and btnode pages. The dirty flag
+ * This function is for both data pages and btnode pages. The dirty flag
* should be treated by caller. The page must not be under i/o.
* Both src and dst page must be locked
*/
@@ -388,7 +388,7 @@ repeat:
}
/**
- * nilfs_copy_back_pages -- copy back pages to orignal cache from shadow cache
+ * nilfs_copy_back_pages -- copy back pages to original cache from shadow cache
* @dmap: destination page cache
* @smap: source page cache
*
diff --git a/fs/nilfs2/segbuf.c b/fs/nilfs2/segbuf.c
index 68b08f2..e3f67c6 100644
--- a/fs/nilfs2/segbuf.c
+++ b/fs/nilfs2/segbuf.c
@@ -174,7 +174,7 @@ int nilfs_segbuf_reset(struct nilfs_segment_buffer *segbuf,
unsigned flags,
}
/*
- * Setup segument summary
+ * Setup segment summary
*/
void nilfs_segbuf_fill_in_segsum(struct nilfs_segment_buffer *segbuf)
{
diff --git a/fs/nilfs2/segment.c b/fs/nilfs2/segment.c
index 3265bfc..69576a9 100644
--- a/fs/nilfs2/segment.c
+++ b/fs/nilfs2/segment.c
@@ -201,7 +201,7 @@ static int nilfs_prepare_segment_lock(struct
nilfs_transaction_info *ti)
* This function allocates a nilfs_transaction_info struct to keep context
* information on it. It is initialized and hooked onto the current task in
* the outermost call. If a pre-allocated struct is given to @ti, it is used
- * instead; othewise a new struct is assigned from a slab.
+ * instead; otherwise a new struct is assigned from a slab.
*
* When @vacancy_check flag is set, this function will check the amount of
* free space, and will wait for the GC to reclaim disk space if low capacity.
@@ -2854,7 +2854,7 @@ static void nilfs_segctor_destroy(struct nilfs_sc_info
*sci)
* @sbi: nilfs_sb_info
*
* nilfs_attach_segment_constructor() allocates a struct nilfs_sc_info,
- * initilizes it, and starts the segment constructor.
+ * initializes it, and starts the segment constructor.
*
* Return Value: On success, 0 is returned. On error, one of the following
* negative error code is returned.
diff --git a/fs/nilfs2/segment.h b/fs/nilfs2/segment.h
index 3155e0c..2a79456 100644
--- a/fs/nilfs2/segment.h
+++ b/fs/nilfs2/segment.h
@@ -30,7 +30,7 @@
#include sb.h
/**
- * struct nilfs_recovery_info - Recovery infomation
+ * struct nilfs_recovery_info - Recovery information
* @ri_need_recovery: Recovery
