{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":2797439,"defaultBranch":"master","name":"nilfs-utils","ownerLogin":"konis","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2011-11-17T17:58:16.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/1105451?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1712149190.0","currentOid":""},"activityList":{"items":[{"before":"58087e8294bbd405ee0b37158c203d64e5876eef","after":"507064bb3604d0fd88f5e3f6422d9ade73a26120","ref":"refs/heads/v2.2.y","pushedAt":"2024-04-03T12:59:50.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"konis","name":"Ryusuke Konishi","path":"/konis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1105451?s=80&v=4"},"commit":{"message":"nilfs-utils: v2.2.11 release\n\nSigned-off-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>","shortMessageHtmlLink":"nilfs-utils: v2.2.11 release"}},{"before":"8a9a5abb3a7ec3b5d1d30bbd851fedcd1488b666","after":"58087e8294bbd405ee0b37158c203d64e5876eef","ref":"refs/heads/v2.2.y","pushedAt":"2024-04-03T11:03:58.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"konis","name":"Ryusuke Konishi","path":"/konis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1105451?s=80&v=4"},"commit":{"message":"libnilfs: fix nilfs_open failure for mount points with escaped characters\n\nnilfs_find_fs(), called from nilfs_open(), parses \"/proc/mounts\" using its\nown routines, but these parsing routines have a problem in that they\ncannot handle escaped path strings.  For example, if the mount point path\nname contains spaces, the search will fail.\n\nThis is causing errors when running lscp, lssu, and other nilfs tools.\n\nFix this issue by avoiding custom parsing and using standard mount table\naccess routines such as setmntent(), getmntent_r(), endmntent(), and\nhasmntopt().\n\nCloses: https://github.com/nilfs-dev/nilfs-utils/issues/22\nSigned-off-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>","shortMessageHtmlLink":"libnilfs: fix nilfs_open failure for mount points with escaped charac…"}},{"before":"dbf8c244ce2dbbe1cbdd77037d636e46ac5402dd","after":"c9b400aa41fb26f9c9d33f9917e027359ab9ef57","ref":"refs/heads/master","pushedAt":"2024-04-03T11:03:31.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"konis","name":"Ryusuke Konishi","path":"/konis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1105451?s=80&v=4"},"commit":{"message":"libnilfs: fix nilfs_open failure for mount points with escaped characters\n\nnilfs_find_fs(), called from nilfs_open(), parses \"/proc/mounts\" using its\nown routines, but these parsing routines have a problem in that they\ncannot handle escaped path strings.  For example, if the mount point path\nname contains spaces, the search will fail.\n\nThis is causing errors when running lscp, lssu, and other nilfs tools.\n\nFix this issue by avoiding custom parsing and using standard mount table\naccess routines such as setmntent(), getmntent_r(), endmntent(), and\nhasmntopt().\n\nCloses: https://github.com/nilfs-dev/nilfs-utils/issues/22\nSigned-off-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>","shortMessageHtmlLink":"libnilfs: fix nilfs_open failure for mount points with escaped charac…"}},{"before":"a34ee4f35fc3a7d718deb925bc4cd56ace018e8b","after":"dbf8c244ce2dbbe1cbdd77037d636e46ac5402dd","ref":"refs/heads/master","pushedAt":"2024-03-16T20:22:33.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"konis","name":"Ryusuke Konishi","path":"/konis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1105451?s=80&v=4"},"commit":{"message":"mkfs.nilfs2: do not use own type blocknr_t\n\nThe block address is now represented by uint64_t, but only mkfs.nilfs2\nuses its own type \"blocknr_t\".\n\nEliminate the own type so that the bit width of variables that handle\nit can be made stricter (such as when displaying).\n\nAdditionally, to avoid obscuring the meaning of \"start\" in identifiers\nintended to be block addresses, rename them to \"start_blocknr\".\n\nSigned-off-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>","shortMessageHtmlLink":"mkfs.nilfs2: do not use own type blocknr_t"}},{"before":"c810fd1b42ba5e2612a057f4d9ca3492d89bf622","after":"8a9a5abb3a7ec3b5d1d30bbd851fedcd1488b666","ref":"refs/heads/v2.2.y","pushedAt":"2024-03-04T11:46:49.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"konis","name":"Ryusuke Konishi","path":"/konis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1105451?s=80&v=4"},"commit":{"message":"nilfs-utils: v2.2.10 release\n\nSigned-off-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>","shortMessageHtmlLink":"nilfs-utils: v2.2.10 release"}},{"before":"26e6e7cefad77844a7bc2a01a635fd74e05117a7","after":"c810fd1b42ba5e2612a057f4d9ca3492d89bf622","ref":"refs/heads/v2.2.y","pushedAt":"2024-03-03T13:54:27.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"konis","name":"Ryusuke Konishi","path":"/konis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1105451?s=80&v=4"},"commit":{"message":"bin/*: correct error message for invalid long option specification\n\nThe commands under \"bin/\" output the error messages by themselves by\nsetting opterr to 0, and are compatible with getopt_long, but if\nan invalid long option is specified, the option that causes the error\nwill not be displayed as shown below:\n\n lscp: invalid option --\n\nAlso lscp and lssu do not properly display error messages for options\nthat require an additional argument and it is not provided.\n\nFix these issues by not setting opterr to 0 and leaving error output\nfor argument options to getopt() or getopt_long()'s built-in features.\n\nSigned-off-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>","shortMessageHtmlLink":"bin/*: correct error message for invalid long option specification"}},{"before":"1003bc3c313fb71d0fb18043424af168d0774311","after":"a34ee4f35fc3a7d718deb925bc4cd56ace018e8b","ref":"refs/heads/master","pushedAt":"2024-03-03T13:39:05.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"konis","name":"Ryusuke Konishi","path":"/konis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1105451?s=80&v=4"},"commit":{"message":"bin/*: correct error message for invalid long option specification\n\nThe commands under \"bin/\" output the error messages by themselves by\nsetting opterr to 0, and are compatible with getopt_long, but if\nan invalid long option is specified, the option that causes the error\nwill not be displayed as shown below:\n\n lscp: invalid option --\n\nAlso lscp and lssu do not properly display error messages for options\nthat require an additional argument and it is not provided.\n\nFix these issues by not setting opterr to 0 and leaving error output\nfor argument options to getopt() or getopt_long()'s built-in features.\n\nSigned-off-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>","shortMessageHtmlLink":"bin/*: correct error message for invalid long option specification"}},{"before":"24c45c4235c08da5e2df6eb925720f85b802b1dc","after":"26e6e7cefad77844a7bc2a01a635fd74e05117a7","ref":"refs/heads/v2.2.y","pushedAt":"2024-03-02T16:00:23.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"konis","name":"Ryusuke Konishi","path":"/konis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1105451?s=80&v=4"},"commit":{"message":"nilfs-resize: make the progress bar more accurate\n\nnilfs_resize_count_inuse_segments() is used to count the segments to\nbe moved in order to evaluate the progress of the progress bar.\nHowever, the current implementation counts segments whose flags are in\nthe reclaimable state (dirty, not active, not error), and does not\ncount active segments, resulting in a discrepancy.\n\nTo represent the progress bar more acculately, change the count to\nliterally \"in-use\" (dirty) segments instead of reclaimable segments.\n\nAlso, there is some confusion regarding the term \"in-use\" in the\ndescription of the nilfs_resize_reclaim() function, so correct that\nas well.\n\nSigned-off-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>","shortMessageHtmlLink":"nilfs-resize: make the progress bar more accurate"}},{"before":"667b0f936baf13b630d248b39d75e4e0336754d3","after":"1003bc3c313fb71d0fb18043424af168d0774311","ref":"refs/heads/master","pushedAt":"2024-03-02T15:05:07.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"konis","name":"Ryusuke Konishi","path":"/konis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1105451?s=80&v=4"},"commit":{"message":"nilfs-resize: make the progress bar more accurate\n\nnilfs_resize_count_inuse_segments() is used to count the segments to\nbe moved in order to evaluate the progress of the progress bar.\nHowever, the current implementation counts segments whose flags are in\nthe reclaimable state (dirty, not active, not error), and does not\ncount active segments, resulting in a discrepancy.\n\nTo represent the progress bar more acculately, change the count to\nliterally \"in-use\" (dirty) segments instead of reclaimable segments.\n\nAlso, there is some confusion regarding the term \"in-use\" in the\ndescription of the nilfs_resize_reclaim() function, so correct that\nas well.\n\nSigned-off-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>","shortMessageHtmlLink":"nilfs-resize: make the progress bar more accurate"}},{"before":"4b982f8a027e0045a7363820cd7b957d5482869c","after":"667b0f936baf13b630d248b39d75e4e0336754d3","ref":"refs/heads/master","pushedAt":"2024-03-02T12:06:04.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"konis","name":"Ryusuke Konishi","path":"/konis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1105451?s=80&v=4"},"commit":{"message":"libnilfsgc: fix potential memory or mmap leak in nilfs_acc_blocks()\n\nIf nilfs_acc_blocks_segment() fails, nilfs_acc_blocks() returns an\nerror without releasing the segment allocated by nilfs_get_segment()\nwith nilfs_put_segment().\n\nFix this potential leak issue by calling nilfs_put_segment() regardless\nof whether the call to nilfs_acc_blocks_segment() is successful or not.\n\nSigned-off-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>","shortMessageHtmlLink":"libnilfsgc: fix potential memory or mmap leak in nilfs_acc_blocks()"}},{"before":"2a11dbb6a80a13297c2047264db2deb543a18a47","after":"24c45c4235c08da5e2df6eb925720f85b802b1dc","ref":"refs/heads/v2.2.y","pushedAt":"2024-03-01T19:51:32.000Z","pushType":"push","commitsCount":6,"pusher":{"login":"konis","name":"Ryusuke Konishi","path":"/konis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1105451?s=80&v=4"},"commit":{"message":"nilfs-resize: force file system update in active segment only situation\n\nIn order to shrink the file system even when there are only active\nsegments in the area to be truncated, force arcive segments to be\nevicted by creating a file (called a balloon file) with the required\nsize on the root directory of the file system and then deleting it.\n\n[ adjusted for v2.2.y ]\n\nSigned-off-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>","shortMessageHtmlLink":"nilfs-resize: force file system update in active segment only situation"}},{"before":"87b1c80fd01a897ea6f1df80b5084dabe07dc673","after":"4b982f8a027e0045a7363820cd7b957d5482869c","ref":"refs/heads/master","pushedAt":"2024-02-29T12:10:46.000Z","pushType":"push","commitsCount":5,"pusher":{"login":"konis","name":"Ryusuke Konishi","path":"/konis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1105451?s=80&v=4"},"commit":{"message":"nilfs-resize: force file system update in active segment only situation\n\nIn order to shrink the file system even when there are only active\nsegments in the area to be truncated, force arcive segments to be\nevicted by creating a file (called a balloon file) with the required\nsize on the root directory of the file system and then deleting it.\n\nSigned-off-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>","shortMessageHtmlLink":"nilfs-resize: force file system update in active segment only situation"}},{"before":"ac9f6c33e817f9aee2eb44a11cc4c7384e6bfcbc","after":"2a11dbb6a80a13297c2047264db2deb543a18a47","ref":"refs/heads/v2.2.y","pushedAt":"2024-02-28T08:44:43.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"konis","name":"Ryusuke Konishi","path":"/konis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1105451?s=80&v=4"},"commit":{"message":"Revert \"lib/nilfs: add freeze and thaw API functions\"\n\nThe recent addition of these functions to the nilfs shared library\nimplementation requires bumping up the library version.\n\nTo avoid bumping up the library version in the maintenance branch\nv2.2.y just to add these wrappers, revert commit 5fc8e71bf2b5\n(\"lib/nilfs: add freeze and thaw API functions\").","shortMessageHtmlLink":"Revert \"lib/nilfs: add freeze and thaw API functions\""}},{"before":"548b15bdf079309a606c27ee63d107000be03dc2","after":"ac9f6c33e817f9aee2eb44a11cc4c7384e6bfcbc","ref":"refs/heads/v2.2.y","pushedAt":"2024-02-27T19:27:33.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"konis","name":"Ryusuke Konishi","path":"/konis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1105451?s=80&v=4"},"commit":{"message":"libnilfs: nilfs_open: use last matched mount\n\nIn the current libnilfs implementation, nilfs_open() returns the first\nmatching mount when searching the mount table.  Therefore, when the\nsame mount points are stacked, the inaccessible mount point will be\nunexpectedly selected.\n\nFix this issue by choosing the last match instead of the first one\nwhen searching the mount table.\n\nThe changes required here also fix potential memory leaks related to\ndevice pathname and mount point pathname strings when nilfs_find_fs()\nis called multiple times.\n\nSigned-off-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>","shortMessageHtmlLink":"libnilfs: nilfs_open: use last matched mount"}},{"before":"74cbae5301b40ac9025bf42e1691f66f24a280fa","after":"87b1c80fd01a897ea6f1df80b5084dabe07dc673","ref":"refs/heads/master","pushedAt":"2024-02-27T18:22:12.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"konis","name":"Ryusuke Konishi","path":"/konis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1105451?s=80&v=4"},"commit":{"message":"libnilfs: nilfs_open: use last matched mount\n\nIn the current libnilfs implementation, nilfs_open() returns the first\nmatching mount when searching the mount table.  Therefore, when the\nsame mount points are stacked, the inaccessible mount point will be\nunexpectedly selected.\n\nFix this issue by choosing the last match instead of the first one\nwhen searching the mount table.\n\nThe changes required here also fixes potential memory leaks related to\ndevice pathname and mount point pathname strings when nilfs_find_fs()\nis called multiple times.\n\nSigned-off-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>","shortMessageHtmlLink":"libnilfs: nilfs_open: use last matched mount"}},{"before":"e884c276c20dbeda5fd84468847d27e85553bc2c","after":"548b15bdf079309a606c27ee63d107000be03dc2","ref":"refs/heads/v2.2.y","pushedAt":"2024-02-25T17:51:25.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"konis","name":"Ryusuke Konishi","path":"/konis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1105451?s=80&v=4"},"commit":{"message":"mkfs.nilfs2, nilfs-resize, nilfs-tune: output error cause when open fails\n\nmkfs.nilfs2, nilfs-resize, and nilfs-tune commands do not display the\nerror cause when they fail to open a nilfs2 device, so add a string\nthat represents the error.\n\nSigned-off-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>","shortMessageHtmlLink":"mkfs.nilfs2, nilfs-resize, nilfs-tune: output error cause when open f…"}},{"before":"ad10d60cd07e53409b44745305dc59d6aa7dac60","after":"74cbae5301b40ac9025bf42e1691f66f24a280fa","ref":"refs/heads/master","pushedAt":"2024-02-25T17:36:51.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"konis","name":"Ryusuke Konishi","path":"/konis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1105451?s=80&v=4"},"commit":{"message":"mkfs.nilfs2, nilfs-resize, nilfs-tune: output error cause when open fails\n\nmkfs.nilfs2, nilfs-resize, and nilfs-tune commands do not display the\nerror cause when they fail to open a nilfs2 device, so add a string\nthat represents the error.\n\nSigned-off-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>","shortMessageHtmlLink":"mkfs.nilfs2, nilfs-resize, nilfs-tune: output error cause when open f…"}},{"before":"e85b5e61141066d5196021f6515c442d5d72294d","after":"e884c276c20dbeda5fd84468847d27e85553bc2c","ref":"refs/heads/v2.2.y","pushedAt":"2024-02-25T16:08:15.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"konis","name":"Ryusuke Konishi","path":"/konis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1105451?s=80&v=4"},"commit":{"message":"umount_libmount: fix error messages\n\nlibmount based umount.nilfs2 does not display the node (target)\ncorrectly in its message on error as below:\n\n umount.nilfs2: (null): device is busy\n\nFix this issue.\n\nSigned-off-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>","shortMessageHtmlLink":"umount_libmount: fix error messages"}},{"before":"15a99ec3431ed28164ad92e624bceaa33bbe40d9","after":"ad10d60cd07e53409b44745305dc59d6aa7dac60","ref":"refs/heads/master","pushedAt":"2024-02-25T15:44:54.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"konis","name":"Ryusuke Konishi","path":"/konis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1105451?s=80&v=4"},"commit":{"message":"umount_libmount: fix error messages\n\nlibmount based umount.nilfs2 does not display the node (target)\ncorrectly in its message on error as below:\n\n umount.nilfs2: (null): device is busy\n\nFix this issue.\n\nSigned-off-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>","shortMessageHtmlLink":"umount_libmount: fix error messages"}},{"before":"7eb742fce31e2e45491f01cb1e3b3798a9ec0753","after":"15a99ec3431ed28164ad92e624bceaa33bbe40d9","ref":"refs/heads/master","pushedAt":"2024-02-25T08:44:33.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"konis","name":"Ryusuke Konishi","path":"/konis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1105451?s=80&v=4"},"commit":{"message":"mkfs.nilfs2: set block_count read-only compat flag by default\n\nThe ability to maintain per-checkpoint block count statistics was enabled\nin kernel 2.6.39, and at the same time a dedicated compat flag\n(NILFS_FEATURE_COMPAT_RO_BLOCK_COUNT) was introduced to prevent this\nblock count from being corrupted by read/write mounts in earlier versions.\n\nMore than 12 years have passed since this flag was introduced, and there\nare almost no opportunities to mount nilfs2 partitions with older kernels\nof this generation (it is not recommended in the first place), so turn on\nthis flag for new file systems created by mkfs.nilfs2.\n\nNote that we can use nilfs-tune command to clear or reset this flag.\n\nSigned-off-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>","shortMessageHtmlLink":"mkfs.nilfs2: set block_count read-only compat flag by default"}},{"before":"f53eb3f99ba367804fba1f7ecc12c9af99a98029","after":"e85b5e61141066d5196021f6515c442d5d72294d","ref":"refs/heads/v2.2.y","pushedAt":"2024-02-24T19:22:37.000Z","pushType":"push","commitsCount":4,"pusher":{"login":"konis","name":"Ryusuke Konishi","path":"/konis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1105451?s=80&v=4"},"commit":{"message":"nilfs-resize: output the minimum device size in insufficient free space message\n\nChange nilfs_resize_check_free_space() to output the required device\nsize instead of the total byte size of the required segments when free\nspace is insufficient.\n\nThis gives a guideline for the device size to be specified when\nrespecifying the device size and retrying shrinking.\n\nSigned-off-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>","shortMessageHtmlLink":"nilfs-resize: output the minimum device size in insufficient free spa…"}},{"before":"0d15f76541d7cb010f3f27b28d9b9ec758c2858c","after":"7eb742fce31e2e45491f01cb1e3b3798a9ec0753","ref":"refs/heads/master","pushedAt":"2024-02-24T18:38:01.000Z","pushType":"push","commitsCount":4,"pusher":{"login":"konis","name":"Ryusuke Konishi","path":"/konis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1105451?s=80&v=4"},"commit":{"message":"nilfs-resize: output the minimum device size in insufficient free space message\n\nChange nilfs_resize_check_free_space() to output the required device\nsize instead of the total byte size of the required segments when free\nspace is insufficient.\n\nThis gives a guideline for the device size to be specified when\nrespecifying the device size and retrying shrinking.\n\nSigned-off-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>","shortMessageHtmlLink":"nilfs-resize: output the minimum device size in insufficient free spa…"}},{"before":"5f0fcf14dcb6e7b4a670da0c53b9c8e789ba440a","after":"f53eb3f99ba367804fba1f7ecc12c9af99a98029","ref":"refs/heads/v2.2.y","pushedAt":"2024-02-23T16:06:42.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"konis","name":"Ryusuke Konishi","path":"/konis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1105451?s=80&v=4"},"commit":{"message":"nilfs-tune: fix usage of wrong endian conversion macro\n\nThe nilfs-tune command's show_nilfs_sb() function, incorrectly uses\nthe 32-bit width conversion macro le32_to_cpu() for two 16-bit width\nfields, so fix them.\n\nSigned-off-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>","shortMessageHtmlLink":"nilfs-tune: fix usage of wrong endian conversion macro"}},{"before":"9050e48ae0aabdf950adebd7df10bf32ef89b583","after":"0d15f76541d7cb010f3f27b28d9b9ec758c2858c","ref":"refs/heads/master","pushedAt":"2024-02-23T15:53:05.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"konis","name":"Ryusuke Konishi","path":"/konis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1105451?s=80&v=4"},"commit":{"message":"nilfs-tune: fix usage of wrong endian conversion macro\n\nThe nilfs-tune command's show_nilfs_sb() function, incorrectly uses\nthe 32-bit width conversion macro le32_to_cpu() for two 16-bit width\nfields, so fix them.\n\nSigned-off-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>","shortMessageHtmlLink":"nilfs-tune: fix usage of wrong endian conversion macro"}},{"before":"53271cb967f57c84d7284a8fe796294bc31e8813","after":"5f0fcf14dcb6e7b4a670da0c53b9c8e789ba440a","ref":"refs/heads/v2.2.y","pushedAt":"2024-02-19T19:04:14.000Z","pushType":"push","commitsCount":7,"pusher":{"login":"konis","name":"Ryusuke Konishi","path":"/konis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1105451?s=80&v=4"},"commit":{"message":"nilfs-tune: do not display version information by default\n\nLike other commands, add the \"-V\" option to display version information\nand suppress output during normal execution.\n\nAlso update help message.\n\nSigned-off-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>","shortMessageHtmlLink":"nilfs-tune: do not display version information by default"}},{"before":"8414cbfe3863f2b382101e5523af8dc908c8ea3d","after":"9050e48ae0aabdf950adebd7df10bf32ef89b583","ref":"refs/heads/master","pushedAt":"2024-02-19T14:48:50.000Z","pushType":"push","commitsCount":7,"pusher":{"login":"konis","name":"Ryusuke Konishi","path":"/konis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1105451?s=80&v=4"},"commit":{"message":"nilfs-tune: do not display version information by default\n\nLike other commands, add the \"-V\" option to display version information\nand suppress output during normal execution.\n\nAlso update the manpage and help messages.\n\nSigned-off-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>","shortMessageHtmlLink":"nilfs-tune: do not display version information by default"}},{"before":"86f4a8117a480a64bffadc5e3a92ef592b421a45","after":"53271cb967f57c84d7284a8fe796294bc31e8813","ref":"refs/heads/v2.2.y","pushedAt":"2024-02-18T13:04:02.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"konis","name":"Ryusuke Konishi","path":"/konis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1105451?s=80&v=4"},"commit":{"message":"lib/sb.c: fix super block read failure from disk image file\n\nUnlike mkfs.nilfs2, nilfs-tune and dumpseg commands will cause errors\nif used directly on a disk image files.  This is because\n__nilfs_sb_read(), which reads superblocks, uses the BLKGETSIZE64 ioctl\ncommand to get the device size, which fails for disk image files.\n\nFix this issue by using the size information obtained from the fstat\nsystem call for regular files.\n\n[ resolved conflicts and build issues with v2.2.y ]\n\nSigned-off-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>","shortMessageHtmlLink":"lib/sb.c: fix super block read failure from disk image file"}},{"before":"4d722cd3eb41f83ab09a1275402c7a3e1f99ce11","after":"8414cbfe3863f2b382101e5523af8dc908c8ea3d","ref":"refs/heads/master","pushedAt":"2024-02-18T12:00:43.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"konis","name":"Ryusuke Konishi","path":"/konis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1105451?s=80&v=4"},"commit":{"message":"lib/sb.c: fix super block read failure from disk image file\n\nUnlike mkfs.nilfs2, nilfs-tune and dumpseg commands will cause errors\nif used directly on a disk image files.  This is because\n__nilfs_sb_read(), which reads superblocks, uses the BLKGETSIZE64 ioctl\ncommand to get the device size, which fails for disk image files.\n\nFix this issue by using the size information obtained from the fstat\nsystem call for regular files.\n\nSigned-off-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>","shortMessageHtmlLink":"lib/sb.c: fix super block read failure from disk image file"}},{"before":"e36c61d8254727c7838f7e98a1a5a1fdb223e86e","after":"86f4a8117a480a64bffadc5e3a92ef592b421a45","ref":"refs/heads/v2.2.y","pushedAt":"2024-02-17T10:12:45.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"konis","name":"Ryusuke Konishi","path":"/konis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1105451?s=80&v=4"},"commit":{"message":"nilfs.h: eliminate sector_t and nilfs_blkoff_t\n\nIt is undesirable for these kernel types and custom generic type\ndefinitions to remain locally in the shared header file for user\nspace, so delete them.\n\nSigned-off-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>","shortMessageHtmlLink":"nilfs.h: eliminate sector_t and nilfs_blkoff_t"}},{"before":"1a289a7a0ad1830e01eb0e6571712fbe1bf498a0","after":"e36c61d8254727c7838f7e98a1a5a1fdb223e86e","ref":"refs/heads/v2.2.y","pushedAt":"2024-02-16T19:14:12.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"konis","name":"Ryusuke Konishi","path":"/konis","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1105451?s=80&v=4"},"commit":{"message":"Make installation of kernel uapi header files optional\n\nThe bundled kernel's uapi header files (\"nilfs2_ondisk.h\" and\n\"nilfs2_api.h\") are included in kernel-related development packages\nin modern Linux distributions, resulting in duplicate installations.\n\nIn order to eliminate this duplication, make the installation of these\nfiles optional and not install them by default.\n\nThe utilities will continue to refer to the included uapi header files,\nand will only allow installation on the system, which can be specified\nusing the \"--enable-uapi-header-install\" option in configure file\narguments.\n\nThis is a workaround for older environments and should normally be\ndisabled.\n\nSigned-off-by: Ryusuke Konishi <konishi.ryusuke@gmail.com>","shortMessageHtmlLink":"Make installation of kernel uapi header files optional"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEJqmlEAA","startCursor":null,"endCursor":null}},"title":"Activity · konis/nilfs-utils"}