From: Nitin Gupta Date: Thu, 30 Dec 2010 09:07:58 +0000 (-0500) Subject: Revert "Staging: zram: work around oops due to startup ordering snafu" X-Git-Tag: v2.6.37~15 X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=e983dc2428164698571e1dd1b25c4322181adbac;p=pandora-kernel.git Revert "Staging: zram: work around oops due to startup ordering snafu" This reverts commit 7e24cce38a99f373450db67bf576fe73e8168d66 because it was never appropriate for mainline. Do not check for init flag before starting I/O - zram module is unusable without this fix. The oops mentioned in the reverted commit message was actually a problem only with the zram version as present in project's own repository where we allocate struct zram_stats_cpu upon device initialization. OTOH, In mainline/staging version of zram, we allocate struct stats upfront, so this oops cannot happen in mainline version. Checking for init_done flag in zram_make_request() results in a *no-op* for any I/O operation since we simply always return success. This flag is actually set when the first write occurs on a zram disk which triggers its initialization. Bug report: https://bugzilla.kernel.org/show_bug.cgi?id=25722 Reported-by: Dennis Jansen Signed-off-by: Nitin Gupta Cc: Anton Blanchard Cc: Andrew Morton Cc: Greg Kroah-Hartman Signed-off-by: Linus Torvalds --- Reading git-diff-tree failed