summaryrefslogtreecommitdiffstats
path: root/Documentation/lockup-watchdogs.txt
diff options
context:
space:
mode:
authorRyusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>2015-02-28 00:51:56 +0100
committerLinus Torvalds <torvalds@linux-foundation.org>2015-02-28 18:57:51 +0100
commit957ed60b53b519064a54988c4e31e0087e47d091 (patch)
tree23b72d64c4b56f4e7eb8c87988158cd4d3d7f730 /Documentation/lockup-watchdogs.txt
parentscripts/gdb: add empty package initialization script (diff)
downloadlinux-957ed60b53b519064a54988c4e31e0087e47d091.tar.xz
linux-957ed60b53b519064a54988c4e31e0087e47d091.zip
nilfs2: fix potential memory overrun on inode
Each inode of nilfs2 stores a root node of a b-tree, and it turned out to have a memory overrun issue: Each b-tree node of nilfs2 stores a set of key-value pairs and the number of them (in "bn_nchildren" member of nilfs_btree_node struct), as well as a few other "bn_*" members. Since the value of "bn_nchildren" is used for operations on the key-values within the b-tree node, it can cause memory access overrun if a large number is incorrectly set to "bn_nchildren". For instance, nilfs_btree_node_lookup() function determines the range of binary search with it, and too large "bn_nchildren" leads nilfs_btree_node_get_key() in that function to overrun. As for intermediate b-tree nodes, this is prevented by a sanity check performed when each node is read from a drive, however, no sanity check has been done for root nodes stored in inodes. This patch fixes the issue by adding missing sanity check against b-tree root nodes so that it's called when on-memory inodes are read from ifile, inode metadata file. Signed-off-by: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp> Cc: <stable@vger.kernel.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'Documentation/lockup-watchdogs.txt')
0 files changed, 0 insertions, 0 deletions