From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: [vfs:master 32/32] fs/open.c:817:18: sparse: restricted fmode_t degrades to integer
Date: Sun, 26 Aug 2012 19:28:29 +0000 [thread overview]
Message-ID: <20120826192829.GA9431@localhost> (raw)
Hi Al,
FYI, there are new sparse warnings show up in
tree: git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git master
head: 9283194882d18e3755c4ebc0b86db9f9a4f4c81a
commit: 9283194882d18e3755c4ebc0b86db9f9a4f4c81a [32/32] don't leak O_CLOEXEC into ->f_flags
All sparse warnings:
+ fs/open.c:817:18: sparse: restricted fmode_t degrades to integer
vim +817 fs/open.c
814 op->mode = 0;
815
816 /* Must never be set by userspace */
> 817 flags &= ~FMODE_NONOTIFY & ~O_CLOEXEC;
818
819 /*
820 * O_SYNC is implemented as __O_SYNC|O_DSYNC. As many places only
---
0-DAY kernel build testing backend Open Source Technology Centre
Fengguang Wu <wfg@linux.intel.com> Intel Corporation
reply other threads:[~2012-08-26 19:28 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=20120826192829.GA9431@localhost \
--to=fengguang.wu@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox