From: Kari Argillander <kari.argillander@gmail.com>
To: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>,
ntfs3@lists.linux.dev
Cc: Kari Argillander <kari.argillander@gmail.com>
Subject: [PATCH 0/2] fs/ntfs3: Fix minor things in ntfs_get_acl_ex()
Date: Thu, 26 Aug 2021 11:35:47 +0300 [thread overview]
Message-ID: <20210826083549.1565173-1-kari.argillander@gmail.com> (raw)
First patch fix Smatch warning.
Second one add missing default path. This is not necessarylly needed,
but will not make any harm and other filesystems have it and it is also
checked some places in ntfs3. So let's be consistent.
Kari Argillander (2):
fs/ntfs3: Fix pass zero to ERR_PTR() in ntfs_get_acl_ex
fs/ntfs3: Fix missing type checking in ntfs_get_acl_ex
fs/ntfs3/xattr.c | 24 +++++++++++++++---------
1 file changed, 15 insertions(+), 9 deletions(-)
--
2.25.1
next reply other threads:[~2021-08-26 8:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 8:35 Kari Argillander [this message]
2021-08-26 8:35 ` [PATCH 1/2] fs/ntfs3: Fix pass zero to ERR_PTR() in ntfs_get_acl_ex Kari Argillander
2021-08-26 9:13 ` Kari Argillander
2021-08-26 8:35 ` [PATCH 2/2] fs/ntfs3: Fix missing type checking " Kari Argillander
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=20210826083549.1565173-1-kari.argillander@gmail.com \
--to=kari.argillander@gmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=ntfs3@lists.linux.dev \
/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