diff for duplicates of <5705089A.3050405@samsung.com> diff --git a/a/1.txt b/N1/1.txt index a0f81e2..8dbcf8a 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -140,23 +140,23 @@ I am running a serious stress test using this patchset. I got a bug as depicted in the below. -<0>[47821.493416] [3: dumpstate:16261] page:ffffffbdc44aaac0 +<0>[47821.493416] [3: dumpstate:16261] page:ffffffbdc44aaac0 count:0 mapcount:0 mapping: (null) index:0x2 <0>[47821.493524] [3: dumpstate:16261] flags: 0x4000000000000000() -<1>[47821.493592] [3: dumpstate:16261] page dumped because: +<1>[47821.493592] [3: dumpstate:16261] page dumped because: VM_BUG_ON_PAGE(!is_first_page(first_page)) -<4>[47821.493684] [3: dumpstate:16261] ------------[ cut here +<4>[47821.493684] [3: dumpstate:16261] ------------[ cut here ]------------ ... -<4>[47821.507309] [3: dumpstate:16261] [<ffffffc0002515f4>] +<4>[47821.507309] [3: dumpstate:16261] [<ffffffc0002515f4>] get_zspage_inuse+0x1c/0x30 -<4>[47821.507381] [3: dumpstate:16261] [<ffffffc0002517a8>] +<4>[47821.507381] [3: dumpstate:16261] [<ffffffc0002517a8>] insert_zspage+0x94/0xb0 -<4>[47821.507452] [3: dumpstate:16261] [<ffffffc000252290>] +<4>[47821.507452] [3: dumpstate:16261] [<ffffffc000252290>] putback_zspage+0xac/0xd4 -<4>[47821.507522] [3: dumpstate:16261] [<ffffffc0002539a0>] +<4>[47821.507522] [3: dumpstate:16261] [<ffffffc0002539a0>] zs_page_migrate+0x3d8/0x464 -<4>[47821.507595] [3: dumpstate:16261] [<ffffffc000250294>] +<4>[47821.507595] [3: dumpstate:16261] [<ffffffc000250294>] migrate_pages+0x5dc/0x88 @@ -174,14 +174,14 @@ I thought that *head page could be a free page in pcp list. Here is my theory. Circumstances -(1) A certain page in a zs page is isolated and about to be migrated. +(1) A certain page in a zs page is isolated and about to be migrated. (not being migrated) -(2) zs_free() simultaneously occurred for the zs object in the above zs +(2) zs_free() simultaneously occurred for the zs object in the above zs page. What may happen. (1) Assume that the above zs_free() made the zspage's FG to ZS_EMPTY. -(2) However, as the zspage is isolated, the zspage is not removed from +(2) However, as the zspage is isolated, the zspage is not removed from the fullness list (e.g. reside in fullness_list[ZS_ALMOST_EMPTY]). (according to this patch's code line just before my greeting.) (3) The zspage is reset by free_zspage() in zs_free(). @@ -637,9 +637,3 @@ Thanks. > } > > - --- -To unsubscribe, send a message with 'unsubscribe linux-mm' in -the body to majordomo@kvack.org. For more info on Linux MM, -see: http://www.linux-mm.org/ . -Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a> diff --git a/a/content_digest b/N1/content_digest index 3233b46..aecb2cf 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -151,23 +151,23 @@ "\n" "I got a bug as depicted in the below.\n" "\n" - "<0>[47821.493416] [3: dumpstate:16261] page:ffffffbdc44aaac0\n" + "<0>[47821.493416] [3: dumpstate:16261] page:ffffffbdc44aaac0 \n" "count:0 mapcount:0 mapping: (null) index:0x2\n" "<0>[47821.493524] [3: dumpstate:16261] flags: 0x4000000000000000()\n" - "<1>[47821.493592] [3: dumpstate:16261] page dumped because:\n" + "<1>[47821.493592] [3: dumpstate:16261] page dumped because: \n" "VM_BUG_ON_PAGE(!is_first_page(first_page))\n" - "<4>[47821.493684] [3: dumpstate:16261] ------------[ cut here\n" + "<4>[47821.493684] [3: dumpstate:16261] ------------[ cut here \n" "]------------\n" "...\n" - "<4>[47821.507309] [3: dumpstate:16261] [<ffffffc0002515f4>]\n" + "<4>[47821.507309] [3: dumpstate:16261] [<ffffffc0002515f4>] \n" "get_zspage_inuse+0x1c/0x30\n" - "<4>[47821.507381] [3: dumpstate:16261] [<ffffffc0002517a8>]\n" + "<4>[47821.507381] [3: dumpstate:16261] [<ffffffc0002517a8>] \n" "insert_zspage+0x94/0xb0\n" - "<4>[47821.507452] [3: dumpstate:16261] [<ffffffc000252290>]\n" + "<4>[47821.507452] [3: dumpstate:16261] [<ffffffc000252290>] \n" "putback_zspage+0xac/0xd4\n" - "<4>[47821.507522] [3: dumpstate:16261] [<ffffffc0002539a0>]\n" + "<4>[47821.507522] [3: dumpstate:16261] [<ffffffc0002539a0>] \n" "zs_page_migrate+0x3d8/0x464\n" - "<4>[47821.507595] [3: dumpstate:16261] [<ffffffc000250294>]\n" + "<4>[47821.507595] [3: dumpstate:16261] [<ffffffc000250294>] \n" "migrate_pages+0x5dc/0x88\n" "\n" "\n" @@ -185,14 +185,14 @@ "Here is my theory.\n" "\n" "Circumstances\n" - "(1) A certain page in a zs page is isolated and about to be migrated.\n" + "(1) A certain page in a zs page is isolated and about to be migrated. \n" "(not being migrated)\n" - "(2) zs_free() simultaneously occurred for the zs object in the above zs\n" + "(2) zs_free() simultaneously occurred for the zs object in the above zs \n" "page.\n" "\n" "What may happen.\n" "(1) Assume that the above zs_free() made the zspage's FG to ZS_EMPTY.\n" - "(2) However, as the zspage is isolated, the zspage is not removed from\n" + "(2) However, as the zspage is isolated, the zspage is not removed from \n" "the fullness list (e.g. reside in fullness_list[ZS_ALMOST_EMPTY]).\n" "(according to this patch's code line just before my greeting.)\n" "(3) The zspage is reset by free_zspage() in zs_free().\n" @@ -647,12 +647,6 @@ "> \tzs_stat_exit();\n" "> }\n" ">\n" - ">\n" - "\n" - "--\n" - "To unsubscribe, send a message with 'unsubscribe linux-mm' in\n" - "the body to majordomo@kvack.org. For more info on Linux MM,\n" - "see: http://www.linux-mm.org/ .\n" - "Don't email: <a href=mailto:\"dont@kvack.org\"> email@kvack.org </a>" + > -8aafc43c2de931ca62840f9910b2c98e0c5412fd5d55497d89e56e347b3d7a3f +c749f5db4ed75400525c8343cffacc8512a0ad32fe4fd7474621cc177465a571
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.