diff options
| author | Artem Bityutskiy <Artem.Bityutskiy@nokia.com> | 2008-11-18 18:09:49 +0200 |
|---|---|---|
| committer | Artem Bityutskiy <Artem.Bityutskiy@nokia.com> | 2008-11-21 18:59:16 +0200 |
| commit | 39ce81ce7168aa7226fb9f182c3a2b57060d0905 (patch) | |
| tree | 8b3c8ff8559c7d3243c0299cae6986aa21601c60 /fs/ubifs/file.c | |
| parent | 7e2d9bfa4eabee3e1919a40f20d2ef8b569bd07e (diff) | |
| download | kernel_samsung_aries-39ce81ce7168aa7226fb9f182c3a2b57060d0905.zip kernel_samsung_aries-39ce81ce7168aa7226fb9f182c3a2b57060d0905.tar.gz kernel_samsung_aries-39ce81ce7168aa7226fb9f182c3a2b57060d0905.tar.bz2 | |
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>
Diffstat (limited to 'fs/ubifs/file.c')
| -rw-r--r-- | fs/ubifs/file.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/fs/ubifs/file.c b/fs/ubifs/file.c index 9124eee..8be827c 100644 --- a/fs/ubifs/file.c +++ b/fs/ubifs/file.c @@ -705,12 +705,12 @@ static int ubifs_do_bulk_read(struct ubifs_info *c, struct page *page1) int err, page_idx, page_cnt, ret = 0, n = 0; loff_t isize; - bu = kmalloc(sizeof(struct bu_info), GFP_NOFS); + bu = kmalloc(sizeof(struct bu_info), GFP_NOFS | __GFP_NOWARN); if (!bu) return 0; bu->buf_len = c->bulk_read_buf_size; - bu->buf = kmalloc(bu->buf_len, GFP_NOFS); + bu->buf = kmalloc(bu->buf_len, GFP_NOFS | __GFP_NOWARN); if (!bu->buf) goto out_free; |