From: "Stephen Biggs" <yrgrknmxpzlk@gawab.com>
To: kernel-janitors@vger.kernel.org
Subject: [KJ] [PATCH][RESUBMIT][16/21] fs/* - compile warning cleanup
Date: Mon, 14 Feb 2005 22:02:53 +0000 [thread overview]
Message-ID: <42113C2D.9148.52C1CA@localhost> (raw)
[-- Attachment #1: Mail message body --]
[-- Type: text/plain, Size: 1258 bytes --]
Description: compile warning cleanup - handle error return warning from
clear_user - the driver writer does not want to check the return value
Signed-off-by: Stephen Biggs <yrgrknmxpzlk@gawab.com>
diff -Nurdp -X dontdiff-osdl linux-2.6.11-rc3-mm2-original/fs/binfmt_elf.c linux-2.6.11-rc3-mm2/fs/binfmt_elf.c
--- linux-2.6.11-rc3-mm2-original/fs/binfmt_elf.c 2005-02-12 12:06:39.000000000 +0200
+++ linux-2.6.11-rc3-mm2/fs/binfmt_elf.c 2005-02-12 13:57:59.000000000 +0200
@@ -823,11 +823,16 @@ static int load_elf_binary(struct linux_
nbyte = elf_brk - elf_bss;
/*
* This bss-zeroing can fail if the ELF file
- * specifies odd protections. So we don't check
- * the return value
+ * specifies odd protections, so we don't want to
+ * check the return value. However, since clear_user() is
+ * declared with attribute 'warn_unused_result', this
+ * causes a warning during compilation. Putting (void)
+ * before the call to clear_user() doesn't silence the warning.
+ * Thus, we need to "trick" the compiler into shutting up.
*/
- (void)clear_user((void __user *)elf_bss +
- load_bias, nbyte);
+ if (clear_user((void __user *)elf_bss +
+ load_bias, nbyte)) {
+ }
}
}
[-- Attachment #2: Type: text/plain, Size: 167 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
reply other threads:[~2005-02-14 22:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42113C2D.9148.52C1CA@localhost \
--to=yrgrknmxpzlk@gawab.com \
--cc=kernel-janitors@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.