[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220518144449.2oa464wnx4p6ovom@wittgenstein>
Date: Wed, 18 May 2022 16:44:49 +0200
From: Christian Brauner <brauner@...nel.org>
To: Vasily Averin <vvs@...nvz.org>
Cc: Christoph Hellwig <hch@...radead.org>, Jan Kara <jack@...e.cz>,
kernel@...nvz.org, linux-kernel@...r.kernel.org,
Alexander Viro <viro@...iv.linux.org.uk>,
Amir Goldstein <amir73il@...il.com>,
Matthew Bobrowski <repnop@...gle.com>,
linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH v2] sparse: fix incorrect fmode_t casts
On Wed, May 18, 2022 at 01:49:07PM +0300, Vasily Averin wrote:
> Fixes sparce warnings:
> fs/notify/fanotify/fanotify_user.c:267:63: sparse:
> warning: restricted fmode_t degrades to integer
> fs/notify/fanotify/fanotify_user.c:1351:28: sparse:
> warning: restricted fmode_t degrades to integer
> fs/proc/base.c:2240:25: sparse: warning: cast to restricted fmode_t
> fs/proc/base.c:2297:42: sparse: warning: cast from restricted fmode_t
> fs/proc/base.c:2394:48: sparse: warning: cast from restricted fmode_t
> fs/open.c:1024:21: sparse: warning: restricted fmode_t degrades to integer
>
> Signed-off-by: Vasily Averin <vvs@...nvz.org>
> ---
Looks good to me,
Reviewed-by: Christian Brauner (Microsoft) <brauner@...nel.org>
Powered by blists - more mailing lists