summaryrefslogtreecommitdiff
path: root/net/l2tp
diff options
context:
space:
mode:
authorDavid Hildenbrand <david@redhat.com>2019-09-24 01:35:46 +0300
committerLinus Torvalds <torvalds@linux-foundation.org>2019-09-25 01:54:09 +0300
commit902ce63b337381092ff865f542e854ff3d0ebe2b (patch)
tree4836506fb32d70cbeb19af136d994b1e65362675 /net/l2tp
parentf915fb7fb2c1c57be05880012b46d2edd5124797 (diff)
downloadlinux-902ce63b337381092ff865f542e854ff3d0ebe2b.tar.xz
driver/base/memory.c: validate memory block size early
Let's validate the memory block size early, when initializing the memory device infrastructure. Fail hard in case the value is not suitable. As nobody checks the return value of memory_dev_init(), turn it into a void function and fail with a panic in all scenarios instead. Otherwise, we'll crash later during boot when core/drivers expect that the memory device infrastructure (including memory_block_size_bytes()) works as expected. I think long term, we should move the whole memory block size configuration (set_memory_block_size_order() and memory_block_size_bytes()) into drivers/base/memory.c. Link: http://lkml.kernel.org/r/20190806090142.22709-1-david@redhat.com Signed-off-by: David Hildenbrand <david@redhat.com> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Cc: "Rafael J. Wysocki" <rafael@kernel.org> Cc: Pavel Tatashin <pasha.tatashin@soleen.com> Cc: Michal Hocko <mhocko@suse.com> Cc: Dan Williams <dan.j.williams@intel.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'net/l2tp')
0 files changed, 0 insertions, 0 deletions