ext4: use WARN in ext4_alloc_blocks
authorJulia Lawall <Julia.Lawall@lip6.fr>
Sat, 2 Feb 2013 01:07:21 +0000 (20:07 -0500)
committerTheodore Ts'o <tytso@mit.edu>
Sat, 2 Feb 2013 01:07:21 +0000 (20:07 -0500)
Use WARN rather than printk followed by WARN_ON(1), for conciseness.

A simplified version of the semantic patch that makes this transformation
is as follows: (http://coccinelle.lip6.fr/)

// <smpl>
@@
expression list es;
@@

-printk(
+WARN(1,
  es);
-WARN_ON(1);
// </smpl>

Signed-off-by: Julia Lawall <Julia.Lawall@lip6.fr>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
fs/ext4/indirect.c

index bdd20231e66c51cbe2eafc0624c7c58eff51fb79..193281098fb64f0aaea26be15a246d1005496f27 100644 (file)
@@ -358,9 +358,8 @@ static int ext4_alloc_blocks(handle_t *handle, struct inode *inode,
                         * for the first direct block
                         */
                        new_blocks[index] = current_block;
-                       printk(KERN_INFO "%s returned more blocks than "
+                       WARN(1, KERN_INFO "%s returned more blocks than "
                                                "requested\n", __func__);
-                       WARN_ON(1);
                        break;
                }
        }