From: "Giedrius Statkevičius" <giedrius.statkevicius@gmail.com>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: "Giedrius Statkevičius" <giedrius.statkevicius@gmail.com>,
lidza.louina@gmail.com, markh@compro.net,
gregkh@linuxfoundation.org,
driverdev-devel@linuxdriverproject.org,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2 RESEND] staging: dgnc: remove dead code in dgnc_tty_write()
Date: Sat, 11 Apr 2015 15:20:43 +0300 (EEST) [thread overview]
Message-ID: <alpine.LNX.2.03.1504111512240.3702@localhost.localdomain> (raw)
In-Reply-To: <20150411045144.GA3496@sudip-PC>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1383 bytes --]
On Sat, 11 Apr 2015, Sudip Mukherjee wrote:
> On Fri, Apr 10, 2015 at 05:48:54PM +0300, Giedrius Statkevičius wrote:
> > Remove the dead code protected by in_user in dgnc_tty_write() because it is set
> > to 0 and never changed to 1 thus the code in ifs never gets executed.
> dgnc_tty_write() is being called by dgnc_tty_put_char() and it is also
> the write callback function of struct tty_operations, so I think the
> correct fix will be to use from_user and make it 0 when
> dgnc_tty_put_char() calls this function else make it 1 to inform the
> function that the data wil be coming from the userspace. Maybe some
> thing like this:
Well, I think this is wrong because:
* parameter of write member of struct tty_operations buf is not tagged with
"__user" so it should be safe to just memcpy() from it
* Looked through some other write operations in other tty drivers and I've never
seen copy_from_user() used on buf argument of write operation - always
memcpy() or some other similar function
* Ldd3 (and the comments in tty_driver.h) says that write could be called from
interrupt context too so it can't sleep and thus use copy_from_user()
While looking through I've caught that dgnc_TmpWriteBuf could be also deleted
because it will be unused if this patch goes through. If it does then I'll send
another one (or should I send a v3?)
Su pagarba / Regards,
Giedrius
next prev parent reply other threads:[~2015-04-11 12:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 14:48 Giedrius Statkevičius
2015-04-10 14:48 ` [PATCH v2 2/2 RESEND] staging: dgnc: remove redundant check Giedrius Statkevičius
2015-04-11 4:51 ` [PATCH v2 1/2 RESEND] staging: dgnc: remove dead code in dgnc_tty_write() Sudip Mukherjee
2015-04-11 12:20 ` Giedrius Statkevičius [this message]
2015-04-11 12:59 ` Sudip Mukherjee
2015-05-03 18:49 ` Greg KH
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=alpine.LNX.2.03.1504111512240.3702@localhost.localdomain \
--to=giedrius.statkevicius@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=lidza.louina@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markh@compro.net \
--cc=sudipm.mukherjee@gmail.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
all inboxes | Powered by JetHome®