From: "Gilad Broner" <gbroner@codeaurora.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: draviv@codeaurora.org, linux-scsi@vger.kernel.org
Subject: re: ufs: add ioctl interface for query request
Date: Mon, 13 Apr 2015 10:55:58 -0000 [thread overview]
Message-ID: <bad58376cabac273fbe5a8ea22356204.squirrel@www.codeaurora.org> (raw)
In-Reply-To: <20150409201755.GA9651@mwanda>
> copy_to/from_user() returns the number of bytes not copied and not an
> error code. Printing these error messages in the ioctl means the user
> can trigger a DoS by filling up /var/log/messages. They make the code
> uglier. We should stop here if the copy fails and goto out_release_mem
> otherwise we might end up returning success by mistake.
Thanks for the comment, I will update the code.
I wanted to clarify about the possibility of a DoS attack:
- Isn't var/log/messages cyclic or size limited in some way?
- What determines that dev_err() prints go to /var/log/messages?
would it still be the case if dev_dbg() was used instead?
Thanks,
Gilad.
--
Qualcomm Israel, on behalf of Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-04-13 10:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 20:17 ufs: add ioctl interface for query request Dan Carpenter
2015-04-13 10:55 ` Gilad Broner [this message]
2015-04-13 11:01 ` 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=bad58376cabac273fbe5a8ea22356204.squirrel@www.codeaurora.org \
--to=gbroner@codeaurora.org \
--cc=dan.carpenter@oracle.com \
--cc=draviv@codeaurora.org \
--cc=linux-scsi@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).