All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: kernel-janitors@vger.kernel.org
Subject: [vfs:master 30/32] fs/proc/fd.c:87:55: sparse: incorrect type in initializer (different base types)
Date: Sun, 26 Aug 2012 19:12:57 +0000	[thread overview]
Message-ID: <20120826191257.GC9107@localhost> (raw)

Hi Cyrill,

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: c8506285ded8009f7c1ab937fc0021c6294ba424 [30/32] procfs: Move /proc/pid/fd[info] handling code to fd.[ch]

All sparse warnings:

+ fs/proc/fd.c:87:55: sparse: incorrect type in initializer (different base types)
  fs/proc/fd.c:87:55:    expected unsigned int [unsigned] f_mode
  fs/proc/fd.c:87:55:    got restricted fmode_t [usertype] f_mode
+ fs/proc/fd.c:105:54: sparse: restricted fmode_t degrades to integer
  fs/proc/fd.c:107:54: sparse: restricted fmode_t degrades to integer

vim +87 fs/proc/fd.c
    84				rcu_read_lock();
    85				file = fcheck_files(files, fd);
    86				if (file) {
  > 87					unsigned f_mode = file->f_mode;
    88	
    89					rcu_read_unlock();
    90					put_files_struct(files);

---
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:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-26 19:12 Fengguang Wu [this message]
2012-08-26 19:26 ` [vfs:master 30/32] fs/proc/fd.c:87:55: sparse: incorrect type in initializer (different base typ Cyrill Gorcunov
2012-08-26 19:52 ` Cyrill Gorcunov
2012-08-26 20:20 ` Al Viro
2012-08-26 20:40 ` Cyrill Gorcunov

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=20120826191257.GC9107@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 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.