summaryrefslogtreecommitdiffstats
path: root/Documentation/zh_CN/volatile-considered-harmful.txt
diff options
context:
space:
mode:
authorArtem Bityutskiy <artem.bityutskiy@linux.intel.com>2012-08-21 13:45:35 +0300
committerArtem Bityutskiy <artem.bityutskiy@linux.intel.com>2012-08-21 15:25:25 +0300
commitc212f4020de7b5d35a71327d1483120a698d60a0 (patch)
treefef68ea74d3a0b111a16fed84fdf130283dc2cdd /Documentation/zh_CN/volatile-considered-harmful.txt
parent11e3be0be2a1314e0861304857e7efcaed5d3e54 (diff)
UBIFS: fix replay regression
Commit "d51f17e UBIFS: simplify reply code a bit" introduces a bug with the following symptoms: UBIFS error (pid 1): replay_log_leb: first CS node at LEB 3:0 has wrong commit number 0 expected 1 The issue is that we start replaying the log from UBIFS_LOG_LNUM instead of c->lhead_lnum. This patch fixes that. Reported-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de> Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
Diffstat (limited to 'Documentation/zh_CN/volatile-considered-harmful.txt')
0 files changed, 0 insertions, 0 deletions