On Thu, Apr 25, 2013 at 01:46:10PM -0700, Andrew Morton wrote: > On Thu, 25 Apr 2013 13:38:35 +0400 Vyacheslav Dubeyko <[email protected]> > wrote: > > > On Thu, 2013-04-25 at 10:49 +0300, Dan Carpenter wrote: > > > [ It's weird that kbuild didn't catch this ]. > > > > > > Hello Vyacheslav Dubeyko, > > > > > > The patch bb594c4767b0: "nilfs2: fix issue with flush kernel thread > > > after remount in RO mode because of driver's internal error or > > > metadata corruption" from Apr 18, 2013, leads to the following > > > warning: > > > "fs/nilfs2/inode.c:211 nilfs_writepage() > > > error: we previously assumed 'inode' could be null (see line 195)" > > > > > > > Please, find below the patch with fix. > > > > Thanks, > > Vyacheslav Dubeyko. > > -- > > From: Vyacheslav Dubeyko <[email protected]> > > Subject: [PATCH] nilfs2: fix warning in nilfs_writepage() > > > > The patch fixes warning: "fs/nilfs2/inode.c:211 nilfs_writepage() error: we > > previously assumed 'inode' could be null (see line 195)". > > The changelog doesn't tell us what tool emitted the warning. Was it sparse? >
That's my fault. It's a Smatch warning. regards, dan carpenter -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
