From mboxrd@z Thu Jan 1 00:00:00 1970 From: Al Viro Subject: Re: [PATCH 2/5] fs: Fix WARN_ON in inode_set_mask() Date: Thu, 4 Dec 2014 14:37:09 +0000 Message-ID: <20141204143708.GM29748@ZenIV.linux.org.uk> References: <1417699659-14284-1-git-send-email-jack@suse.cz> <1417699659-14284-3-git-send-email-jack@suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: linux-fsdevel@vger.kernel.org, linux-security-module@vger.kernel.org, xfs@oss.sgi.com To: Jan Kara Return-path: Content-Disposition: inline In-Reply-To: <1417699659-14284-3-git-send-email-jack@suse.cz> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com List-Id: linux-fsdevel.vger.kernel.org On Thu, Dec 04, 2014 at 02:27:36PM +0100, Jan Kara wrote: > WARN_ON in inode_set_mask() warns if we don't clear all bits we are > setting instead of reverse - warning when caller requests setting and > clearing of the same bit. WTF? 'mask' is "all bits we are asked to modify", 'flags' - "the values to put into those bits". Have you even looked at the callers, let alone tested it? _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs