From: Dan Carpenter <dan.carpenter@oracle.com>
To: jack@suse.cz
Cc: linux-ext4@vger.kernel.org
Subject: [bug report] ext4: Set flags on quota files directly
Date: Wed, 15 Dec 2021 14:42:31 +0300 [thread overview]
Message-ID: <20211215114231.GA12626@kili> (raw)
Hello Jan Kara,
The patch 957153fce8d2: "ext4: Set flags on quota files directly"
from Apr 6, 2017, leads to the following Smatch static checker
warning:
fs/ext4/super.c:6779 ext4_quota_on()
warn: missing error code here? 'IS_ERR()' failed. 'err' = '0'
fs/ext4/super.c
6761
6762 lockdep_set_quota_inode(path->dentry->d_inode, I_DATA_SEM_QUOTA);
6763 err = dquot_quota_on(sb, type, format_id, path);
6764 if (err) {
6765 lockdep_set_quota_inode(path->dentry->d_inode,
6766 I_DATA_SEM_NORMAL);
6767 } else {
6768 struct inode *inode = d_inode(path->dentry);
6769 handle_t *handle;
6770
6771 /*
6772 * Set inode flags to prevent userspace from messing with quota
6773 * files. If this fails, we return success anyway since quotas
6774 * are already enabled and this is not a hard failure.
6775 */
6776 inode_lock(inode);
6777 handle = ext4_journal_start(inode, EXT4_HT_QUOTA, 1);
6778 if (IS_ERR(handle))
--> 6779 goto unlock_inode;
This should set "err = PTR_ERR(handle)" right?
6780 EXT4_I(inode)->i_flags |= EXT4_NOATIME_FL | EXT4_IMMUTABLE_FL;
6781 inode_set_flags(inode, S_NOATIME | S_IMMUTABLE,
6782 S_NOATIME | S_IMMUTABLE);
6783 err = ext4_mark_inode_dirty(handle, inode);
6784 ext4_journal_stop(handle);
6785 unlock_inode:
6786 inode_unlock(inode);
6787 }
6788 return err;
6789 }
regards,
dan carpenter
next reply other threads:[~2021-12-15 11:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 11:42 Dan Carpenter [this message]
2021-12-15 11:59 ` [bug report] ext4: Set flags on quota files directly Jan Kara
2021-12-15 12:05 ` Dan Carpenter
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=20211215114231.GA12626@kili \
--to=dan.carpenter@oracle.com \
--cc=jack@suse.cz \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).