| commit | 39ce81ce7168aa7226fb9f182c3a2b57060d0905 | |
| author | Artem Bityutskiy <Artem.Bityutskiy@nokia.com> | |
| Tue, 18 Nov 2008 16:09:49 +0000 (18 18:09 +0200) | ||
| committer | Artem Bityutskiy <Artem.Bityutskiy@nokia.com> | |
| Fri, 21 Nov 2008 16:59:16 +0000 (21 18:59 +0200) | ||
| tree | 8b3c8ff8559c7d3243c0299cae6986aa21601c60 | treesnapshot (tar.gz zip) |
| parent | 7e2d9bfa4eabee3e1919a40f20d2ef8b569bd07e | commitdiff |
UBIFS: do not print scary memory allocation warnings
Bulk-read allocates a lot of memory with 'kmalloc()', and when it
is/gets fragmented 'kmalloc()' fails with a scarry warning. But
because bulk-read is just an optimization, UBIFS keeps working fine.
Supress the warning by passing __GFP_NOWARN option to 'kmalloc()'.
This patch also introduces a macro for the magic 128KiB constant.
This is just neater.
Note, this is not really fixes the problem we had, but just hides
the warnings. The further patches fix the problem.
Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
Bulk-read allocates a lot of memory with 'kmalloc()', and when it
is/gets fragmented 'kmalloc()' fails with a scarry warning. But
because bulk-read is just an optimization, UBIFS keeps working fine.
Supress the warning by passing __GFP_NOWARN option to 'kmalloc()'.
This patch also introduces a macro for the magic 128KiB constant.
This is just neater.
Note, this is not really fixes the problem we had, but just hides
the warnings. The further patches fix the problem.
Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
| fs/ubifs/file.c | diffblobblamehistory | |
| fs/ubifs/super.c | diffblobblamehistory | |
| fs/ubifs/ubifs.h | diffblobblamehistory |