From: Payal Kshirsagar <payalskshirsagar1234@gmail.com>
To: linux-kernel@vger.kernel.org, outreachy-kernel@googlegroups.com
Cc: Payal Kshirsagar <payalskshirsagar1234@gmail.com>
Subject: [PATCH] ipc: add blank lines after declarations
Date: Mon, 30 Mar 2020 16:13:06 +0530 [thread overview]
Message-ID: <20200330104306.6672-1-payalskshirsagar1234@gmail.com> (raw)
Fix checkpatch.pl warning by adding blank lines.
Signed-off-by: Payal Kshirsagar <payalskshirsagar1234@gmail.com>
---
ipc/compat.c | 2 ++
ipc/ipc_sysctl.c | 2 ++
2 files changed, 4 insertions(+)
diff --git a/ipc/compat.c b/ipc/compat.c
index 5ab8225923af..6c03927a4d71 100644
--- a/ipc/compat.c
+++ b/ipc/compat.c
@@ -39,6 +39,7 @@ int get_compat_ipc64_perm(struct ipc64_perm *to,
struct compat_ipc64_perm __user *from)
{
struct compat_ipc64_perm v;
+
if (copy_from_user(&v, from, sizeof(v)))
return -EFAULT;
to->uid = v.uid;
@@ -51,6 +52,7 @@ int get_compat_ipc_perm(struct ipc64_perm *to,
struct compat_ipc_perm __user *from)
{
struct compat_ipc_perm v;
+
if (copy_from_user(&v, from, sizeof(v)))
return -EFAULT;
to->uid = v.uid;
diff --git a/ipc/ipc_sysctl.c b/ipc/ipc_sysctl.c
index affd66537e87..ea115dfd3774 100644
--- a/ipc/ipc_sysctl.c
+++ b/ipc/ipc_sysctl.c
@@ -18,6 +18,7 @@ static void *get_ipc(struct ctl_table *table)
{
char *which = table->data;
struct ipc_namespace *ipc_ns = current->nsproxy->ipc_ns;
+
which = (which - (char *)&init_ipc_ns) + (char *)ipc_ns;
return which;
}
@@ -62,6 +63,7 @@ static int proc_ipc_doulongvec_minmax(struct ctl_table *table, int write,
void __user *buffer, size_t *lenp, loff_t *ppos)
{
struct ctl_table ipc_table;
+
memcpy(&ipc_table, table, sizeof(ipc_table));
ipc_table.data = get_ipc(table);
--
2.17.1
reply other threads:[~2020-03-30 10:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200330104306.6672-1-payalskshirsagar1234@gmail.com \
--to=payalskshirsagar1234@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=outreachy-kernel@googlegroups.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 NNTP newsgroup(s).