| commit | 73bbbf5c69310387ffa7c948ecef4fbe03c45bf0 | |
| author | Dan Carpenter <dan.carpenter@oracle.com> | |
| Mon, 27 Apr 2015 13:44:16 +0000 (27 16:44 +0300) | ||
| committer | Dan Carpenter <dan.carpenter@oracle.com> | |
| Mon, 27 Apr 2015 13:44:16 +0000 (27 16:44 +0300) | ||
| tree | e59a9c4711ce185e4efb399b083ce6362fbf8d15 | treesnapshot (tar.gz zip) |
| parent | 4bec9016647ab6b82981e41544c4f2f4ce943d7f | commitdiff |
fixup_kernel: kmalloc() can allocate more data. Let's say 4MB.
The actual amount of data that kmalloc() can allocate depends on the
config. I'm not sure why I have 128k here. I think I meant 128MB, since
that is a the answer in some configs. There is at least one place which
relies on kmalloc() to allocate a 1MB chunk of data. Smatch was assuming
it failed every time. That creates hard to understand false positives.
So let's boost it up and say that kmalloc can allocate up to 4MB.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
The actual amount of data that kmalloc() can allocate depends on the
config. I'm not sure why I have 128k here. I think I meant 128MB, since
that is a the answer in some configs. There is at least one place which
relies on kmalloc() to allocate a 1MB chunk of data. Smatch was assuming
it failed every time. That creates hard to understand false positives.
So let's boost it up and say that kmalloc can allocate up to 4MB.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
| smatch_data/db/fixup_kernel.sh | diffblobblamehistory |