summaryrefslogtreecommitdiff
path: root/fs/overlayfs
diff options
context:
space:
mode:
authorDaniel Thompson <daniel.thompson@linaro.org>2014-10-27 18:51:43 +0000
committerAl Viro <viro@zeniv.linux.org.uk>2014-10-28 18:24:30 -0400
commit5fecf3a1e1a0af61eb34eb6976ec9f59cca65d3f (patch)
tree3ce7295f4f7429418339fe3d47c4c996dafbbc8d /fs/overlayfs
parentcac7f2429872d3733dc3f9915857b1691da2eb2f (diff)
staging: android: logger: Fix log corruption regression
Since commit cd678fce4280 ("switch logger to ->write_iter()"), any attempt to write to the log results in the log data being written over its own metadata, thus rendering the log unreadable. The problem was first detected when I ran an Android userspace on the v3.18-rc1 kernel. However the issue can also be observed with a non-Android userspace by using echo/cat to write to/from /dev/log_main . This patch resolves the problem by using a temporary to track the status of not-yet-committed writes to the log buffer. Signed-off-by: Daniel Thompson <daniel.thompson@linaro.org> Cc: Al Viro <viro@zeniv.linux.org.uk> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'fs/overlayfs')
0 files changed, 0 insertions, 0 deletions