)]}' { "log": [ { "commit": "b36a261e8c0ab323d04db9cdd1f6bb4c273c4b32", "tree": "00c90c5fa556f335338f4f61c808d4dfe502bb74", "parents": [ "0964f6a27b3574d9210c59ec883cbb3fff78a78d" ], "author": { "name": "Richard Weinberger", "email": "richard@nod.at", "time": "Mon May 14 17:55:51 2012 +0200" }, "committer": { "name": "Artem Bityutskiy", "email": "artem.bityutskiy@linux.intel.com", "time": "Sun May 20 20:25:59 2012 +0300" }, "message": "UBI: Kill data type hint\n\nWe do not need this feature and to our shame it even was not working\nand there was a bug found very recently.\n\t-- Artem Bityutskiy\n\nWithout the data type hint UBI2 (fastmap) will be easier to implement.\n\nSigned-off-by: Richard Weinberger \u003crichard@nod.at\u003e\nSigned-off-by: Artem Bityutskiy \u003cartem.bityutskiy@linux.intel.com\u003e\n" }, { "commit": "edf6be245fd34a4438646375cecb11f5feb92646", "tree": "ca1ddfc1900d5875d5434c6c7f39ca4966ef3baa", "parents": [ "7c46d0ae29ba880963db283706950de7aa86c0a0" ], "author": { "name": "Artem Bityutskiy", "email": "artem.bityutskiy@linux.intel.com", "time": "Wed May 16 19:15:56 2012 +0300" }, "committer": { "name": "Artem Bityutskiy", "email": "artem.bityutskiy@linux.intel.com", "time": "Wed May 16 19:15:56 2012 +0300" }, "message": "UBIFS: rename dumping functions\n\nThis commit re-names all functions which dump something from \"dbg_dump_*()\" to\n\"ubifs_dump_*()\". This is done for consistency with UBI and because this way it\nwill be more logical once we remove the debugging sompilation option.\n\nSigned-off-by: Artem Bityutskiy \u003cartem.bityutskiy@linux.intel.com\u003e\n" }, { "commit": "b137545c44fc0c80fb778abb0c582bda5601e8f8", "tree": "fb3da759a3c64587bee8bacf408cf774adb8b09a", "parents": [ "cc64f774b4acd4954abe54f5919f50d78aba1e5f" ], "author": { "name": "Artem Bityutskiy", "email": "Artem.Bityutskiy@nokia.com", "time": "Tue Mar 29 18:04:05 2011 +0300" }, "committer": { "name": "Artem Bityutskiy", "email": "Artem.Bityutskiy@nokia.com", "time": "Fri May 13 19:23:53 2011 +0300" }, "message": "UBIFS: introduce a separate structure for budgeting info\n\nThis patch separates out all the budgeting-related information\nfrom \u0027struct ubifs_info\u0027 to \u0027struct ubifs_budg_info\u0027. This way the\ncode looks a bit cleaner. However, the main driver for this is\nthat we want to save budgeting information and print it later,\nso a separate data structure for this is helpful.\n\nThis patch is a preparation for the further debugging output\nimprovements.\n\nSigned-off-by: Artem Bityutskiy \u003cArtem.Bityutskiy@nokia.com\u003e\n" }, { "commit": "2ef13294d29bcfb306e0d360f1b97f37b647b0c0", "tree": "877e1ece00c14de0f0d79e86b6480d284d309216", "parents": [ "2680d722bf2c5f75225dd9acb3ec9e5a9e2652f4" ], "author": { "name": "Artem Bityutskiy", "email": "Artem.Bityutskiy@nokia.com", "time": "Sun Sep 19 18:34:26 2010 +0300" }, "committer": { "name": "Artem Bityutskiy", "email": "Artem.Bityutskiy@nokia.com", "time": "Sun Sep 19 21:07:58 2010 +0300" }, "message": "UBIFS: introduce new flags for RO mounts\n\nCommit 2fde99cb55fb9d9b88180512a5e8a5d939d27fec \"UBIFS: mark VFS SB RO too\"\nintroduced regression. This commit made UBIFS set the \u0027MS_RDONLY\u0027 flag in the\nVFS superblock when it switches to R/O mode due to an error. This was done\nto make VFS show the R/O UBIFS flag in /proc/mounts.\n\nHowever, several places in UBIFS relied on the \u0027MS_RDONLY\u0027 flag and assume this\nflag can only change when we re-mount. For example, \u0027ubifs_put_super()\u0027.\n\nThis patch introduces new UBIFS flag - \u0027c-\u003ero_mount\u0027 which changes only when\nwe re-mount, and preserves the way UBIFS was originally mounted (R/W or R/O).\nThis allows us to de-initialize UBIFS cleanly in \u0027ubifs_put_super()\u0027.\n\nThis patch also changes all \u0027ubifs_assert(!c-\u003ero_media)\u0027 assertions to\n\u0027ubifs_assert(!c-\u003ero_media \u0026\u0026 !c-\u003ero_mount)\u0027, because we never should write\nanything if the FS was mounter R/O.\n\nAll the places where we test for \u0027MS_RDONLY\u0027 flag in the VFS SB were changed\nand now we test the \u0027c-\u003ero_mount\u0027 flag instead, because it preserves the\noriginal UBIFS mount type, unlike the \u0027MS_RDONLY\u0027 flag.\n\nSigned-off-by: Artem Bityutskiy \u003cArtem.Bityutskiy@nokia.com\u003e\n" }, { "commit": "2680d722bf2c5f75225dd9acb3ec9e5a9e2652f4", "tree": "af016ede5f300a33ddd3ad66a8c3c0e6bf05774e", "parents": [ "8c893a5545ca772744376295690723dcb0b47d96" ], "author": { "name": "Artem Bityutskiy", "email": "Artem.Bityutskiy@nokia.com", "time": "Fri Sep 17 16:44:28 2010 +0300" }, "committer": { "name": "Artem Bityutskiy", "email": "Artem.Bityutskiy@nokia.com", "time": "Fri Sep 17 17:08:09 2010 +0300" }, "message": "UBIFS: introduce new flag for RO due to errors\n\nThe R/O state may have various reasons:\n\n1. The UBI volume is R/O\n2. The FS is mounted R/O\n3. The FS switched to R/O mode because of an error\n\nHowever, in UBIFS we have only one variable which represents cases\n1 and 3 - \u0027c-\u003ero_media\u0027. Indeed, we set this to 1 if we switch to\nR/O mode due to an error, and then we test it in many places to\nmake sure that we stop writing as soon as the error happens.\n\nBut this is very unclean. One consequence of this, for example, is\nthat in \u0027ubifs_remount_fs()\u0027 we use \u0027c-\u003ero_media\u0027 to check whether\nwe are in R/O mode because on an error, and we print a message\nin this case. However, if we are in R/O mode because the media\nis R/O, our message is bogus.\n\nThis patch introduces new flag - \u0027c-\u003ero_error\u0027 which is set when\nwe switch to R/O mode because of an error. It also changes all\n\"if (c-\u003ero_media)\" checks to \"if (c-\u003ero_error)\" checks, because\nthis is what the checks actually mean. We do not need to check\nfor \u0027c-\u003ero_media\u0027 because if the UBI volume is in R/O mode, we\ndo not allow R/W mounting, and now writes can happen. This is\nguaranteed by VFS. But it is good to double-check this, so this\npatch also adds many \"ubifs_assert(!c-\u003ero_media)\" checks.\n\nIn the \u0027ubifs_remount_fs()\u0027 function this patch makes a bit more\nchanges - it fixes the error messages as well.\n\nSigned-off-by: Artem Bityutskiy \u003cArtem.Bityutskiy@nokia.com\u003e\n" }, { "commit": "0dcd18e4073454daf591e7127247e32ec942b4f3", "tree": "2f9e0175bc1af2e841269c19f0a5f65cc22088d7", "parents": [ "348709bad348d2fd013e1529b4cf5f220717c328" ], "author": { "name": "Artem Bityutskiy", "email": "Artem.Bityutskiy@nokia.com", "time": "Tue Aug 25 16:22:53 2009 +0300" }, "committer": { "name": "Artem Bityutskiy", "email": "Artem.Bityutskiy@nokia.com", "time": "Thu Sep 10 12:06:47 2009 +0300" }, "message": "UBIFS: check ubifs_scan error codes better\n\nThe \u0027ubifs_scan()\u0027 function returns -EUCLEAN if something is corrupted\nand recovery is needed, otherwise it returns other error codes. However,\nin few places UBIFS does not check the error codes and runs recovery.\nThis patch changes this behavior and makes UBIFS start recovery only\non -EUCLEAN errors.\n\nSigned-off-by: Artem Bityutskiy \u003cArtem.Bityutskiy@nokia.com\u003e\nReviewed-by: Adrian Hunter \u003cAdrian.Hunter@nokia.com\u003e\n" }, { "commit": "348709bad348d2fd013e1529b4cf5f220717c328", "tree": "e5ba0fb86c1c41d078c38f6ca67bda957241ef53", "parents": [ "e3c3efc243462d67ba9fa7f67620dcbc4597bf0a" ], "author": { "name": "Artem Bityutskiy", "email": "Artem.Bityutskiy@nokia.com", "time": "Tue Aug 25 15:00:55 2009 +0300" }, "committer": { "name": "Artem Bityutskiy", "email": "Artem.Bityutskiy@nokia.com", "time": "Thu Sep 10 12:06:47 2009 +0300" }, "message": "UBIFS: do not print scary error messages needlessly\n\nAt the moment UBIFS print large and scary error messages and\nflash dumps in case of nearly any corruption, even if it is\na recoverable corruption. For example, if the master node is\ncorrupted, ubifs_scan() prints error dumps, then UBIFS recovers\njust fine and goes on.\n\nThis patch makes UBIFS print scary error messages only in\nreal cases, which are not recoverable. It adds \u0027quiet\u0027 argument\nto the \u0027ubifs_scan()\u0027 function, so the caller may ask \u0027ubi_scan()\u0027\nnot to print error messages if the caller is able to do recovery.\n\nSigned-off-by: Artem Bityutskiy \u003cArtem.Bityutskiy@nokia.com\u003e\nReviewed-by: Adrian Hunter \u003cAdrian.Hunter@nokia.com\u003e\n" }, { "commit": "a2b9df3ff691db8e5e521dccd231a8098bbf7416", "tree": "50a12bd4d40a27d7a605aa55e3d770b4af3c8576", "parents": [ "b466f17d780c5b72427f36aef22ecdec9f1d0689" ], "author": { "name": "Artem Bityutskiy", "email": "Artem.Bityutskiy@nokia.com", "time": "Thu Jan 29 16:22:54 2009 +0200" }, "committer": { "name": "Artem Bityutskiy", "email": "Artem.Bityutskiy@nokia.com", "time": "Thu Jan 29 16:22:54 2009 +0200" }, "message": "UBIFS: return sensible error codes\n\nWhen mounting/re-mounting, UBIFS returns EINVAL even if the ENOSPC\nor EROFS codes are are much better, just because we have not found\nreferences to ENOSPC/EROFS in mount (2) man pages. This patch\nchanges this behaviour and makes UBIFS return real error code,\nbecause:\n\n1. It is just less confusing and more logical\n2. mount is not described in SuSv3, so it seems to be not really\n well-standartized\n3. we do not cover all cases, and any random undocumented in man\n pages error code may be returned anyway\n\nSigned-off-by: Artem Bityutskiy \u003cArtem.Bityutskiy@nokia.com\u003e\n" }, { "commit": "1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d", "tree": "919debdd48aef9eee9ff0e8f465ef2649325b993", "parents": [ "e56a99d5a42dcb91e622ae7a0289d8fb2ddabffb" ], "author": { "name": "Artem Bityutskiy", "email": "Artem.Bityutskiy@nokia.com", "time": "Mon Jul 14 19:08:37 2008 +0300" }, "committer": { "name": "Artem Bityutskiy", "email": "Artem.Bityutskiy@nokia.com", "time": "Tue Jul 15 17:35:15 2008 +0300" }, "message": "UBIFS: add new flash file system\n\nThis is a new flash file system. See\nhttp://www.linux-mtd.infradead.org/doc/ubifs.html\n\nSigned-off-by: Artem Bityutskiy \u003cArtem.Bityutskiy@nokia.com\u003e\nSigned-off-by: Adrian Hunter \u003cext-adrian.hunter@nokia.com\u003e\n" } ] }