From: Srikanth Korangala Hari <srikanth.h@samsung.com>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: "keescook@chromium.org" <keescook@chromium.org>,
"adobriyan@gmail.com" <adobriyan@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
Srikanth Korangala Hari <srikanth.h@samsung.com>
Subject: RE: Re: [PATCH 1/1] Preventive patch in the proc file-system to handle NULL check.
Date: Fri, 17 Aug 2018 08:51:42 +0530 [thread overview]
Message-ID: <20180817032142epcms5p875c72643ea624e3b2d8f10e4abaf5182@epcms5p8> (raw)
In-Reply-To: <20180816131731.GB1457@garbanzo.do-not-panic.com>
> Thanks for the patch! Do you have a reproducer or is this theoretical?
> This will affect if it should go to stable or not.
Dear Luis, this is theoretical as I observed in most of the call's to api - "proc_mkdir" the NULL check is being done. Hence I thought of adding one here.
Regards,
Srikanth
next prev parent reply other threads:[~2018-08-17 6:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180816093424epcas2p25ede075fec715ad31108360ddca9cce8@epcas2p2.samsung.com>
2018-08-16 9:34 ` [PATCH 1/1] Preventive patch in the proc file-system to handle NULL check Srikanth K H
2018-08-16 12:32 ` Alexey Dobriyan
2018-08-16 13:17 ` Luis Chamberlain
[not found] ` <CGME20180816093424epcas2p25ede075fec715ad31108360ddca9cce8@epcms5p8>
2018-08-17 3:21 ` Srikanth Korangala Hari [this message]
2018-08-17 3:36 ` Al Viro
[not found] ` <CGME20180816093424epcas2p25ede075fec715ad31108360ddca9cce8@epcms5p1>
2018-08-17 3:27 ` Srikanth Korangala Hari
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=20180817032142epcms5p875c72643ea624e3b2d8f10e4abaf5182@epcms5p8 \
--to=srikanth.h@samsung.com \
--cc=adobriyan@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@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).