From: SF Markus Elfring <elfring@users.sourceforge.net>
To: ecryptfs@vger.kernel.org, Tyler Hicks <tyhicks@canonical.com>
Cc: LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org
Subject: [PATCH 0/3] eCryptfs: Adjustments for several function implementations
Date: Sat, 19 Aug 2017 18:54:14 +0200 [thread overview]
Message-ID: <56e0a575-2a9e-120f-6a22-96d9fa4b151e@users.sourceforge.net> (raw)
From: Markus Elfring <elfring@users.sourceforge.net>
Date: Sat, 19 Aug 2017 18:15:14 +0200
Some update suggestions were taken into account
from static source code analysis.
Markus Elfring (3):
Delete 21 error messages for a failed memory allocation
Return an error code only as a constant in ecryptfs_add_global_auth_tok()
Adjust four checks for null pointers
fs/ecryptfs/crypto.c | 22 +++-------------------
fs/ecryptfs/inode.c | 3 ---
fs/ecryptfs/keystore.c | 46 +++++++++++-----------------------------------
fs/ecryptfs/messaging.c | 6 ------
fs/ecryptfs/miscdev.c | 6 +-----
fs/ecryptfs/mmap.c | 2 --
6 files changed, 15 insertions(+), 70 deletions(-)
--
2.14.0
next reply other threads:[~2017-08-19 16:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-19 16:54 SF Markus Elfring [this message]
2017-08-19 16:55 ` [PATCH 1/3] ecryptfs: Delete 21 error messages for a failed memory allocation SF Markus Elfring
2017-08-19 16:56 ` [PATCH 2/3] ecryptfs: Return an error code only as a constant in ecryptfs_add_global_auth_tok() SF Markus Elfring
2017-08-19 16:57 ` [PATCH 3/3] ecryptfs: Adjust four checks for null pointers SF Markus Elfring
2017-10-14 1:29 ` [PATCH 0/3] eCryptfs: Adjustments for several function implementations Tyler Hicks
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=56e0a575-2a9e-120f-6a22-96d9fa4b151e@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=ecryptfs@vger.kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tyhicks@canonical.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).