diff options
| author | Brian Behlendorf <[email protected]> | 2010-08-26 09:52:40 -0700 |
|---|---|---|
| committer | Brian Behlendorf <[email protected]> | 2010-08-27 15:34:02 -0700 |
| commit | 0e5b68e0159e071dae2cac01c2b6783b8e926133 (patch) | |
| tree | 831cd00c0a79b73297f7d6b051ce47a02e523fd5 /lib/libzpool | |
| parent | f709a82dc11fe9bad4953e9cfb0a78f71c859ff0 (diff) | |
Fix gcc fortify source warnings
Resolve issues uncovered by -D_FORTIFY_SOURCE=2, the default redhat
macro's file adds this option to the cflags. This causes warnings
of the following type designed to keep the developer honest:
warning: ignoring return value of 'foo', declared
with attribute warn_unused_result
The short term fix is to wrap these calls in VERIFY() to check the
return code. The code was already assusing these would never fail.
Signed-off-by: Brian Behlendorf <[email protected]>
Diffstat (limited to 'lib/libzpool')
| -rw-r--r-- | lib/libzpool/kernel.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/lib/libzpool/kernel.c b/lib/libzpool/kernel.c index f323bf60b..ef264061f 100644 --- a/lib/libzpool/kernel.c +++ b/lib/libzpool/kernel.c @@ -796,7 +796,7 @@ umem_out_of_memory(void) { char errmsg[] = "out of memory -- generating core dump\n"; - write(fileno(stderr), errmsg, sizeof (errmsg)); + (void) fprintf(stderr, "%s", errmsg); abort(); return (0); } |