ocfs2-devel.oss.oracle.com archive mirror
 help / color / mirror / Atom feed
From: Joel Becker <Joel.Becker@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 1/1] Ocfs2: Add new OCFS2_IOC_INFO ioctl for ocfs2 v7.
Date: Mon, 10 May 2010 23:51:06 -0700	[thread overview]
Message-ID: <20100511065106.GA16757@mail.oracle.com> (raw)
In-Reply-To: <4BE8BCF0.8040104@oracle.com>

On Tue, May 11, 2010 at 10:12:00AM +0800, tristan wrote:
> Joel Becker wrote:
> > static inline void __o2info_error_to_user(struct ocfs2_info_request *kreq,
> > 					  struct ocfs2_info_request __user *req)
> > {
> > 	kreq->ir_flags |= OCFS2_INFO_FL_ERROR;
> > 	(void)o2info_to_user(kreq, req);
> 
> I thought we'd better not pass the whole ocfs2_info_request body this 
> time, but passing only ir_flags instead.
> 
> kreq->ir_flags |= OCFS2_INFO_FL_ERROR;
> 
> put_user(kreq->ir_flags, (__u32 user *)&(req->ir_flags));

	Yep, this is better.  As you say, the full copy is overkill.

> Another corner:
> 
> How about if we hit -EFAULT again when sending the FL_ERROR to 
> userpsace? actually I guess it's quite likely to happen since we've had 
> already failed to pass the request body last time.

	I expect we might.  We just ignore that error.  The user is
still going to get the error code back via the return code of ioctl().
Essentially it's just a best effort.  If we got -EFAULT on the entire
copy, maybe the put_user() works, maybe it doesn't.  Gives the user a
chance to check.
Joel

-- 

"We will have to repent in this generation not merely for the
 vitriolic words and actions of the bad people, but for the 
 appalling silence of the good people."
	- Rev. Dr. Martin Luther King, Jr.

Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127

  reply	other threads:[~2010-05-11  6:51 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-06  8:43 [Ocfs2-devel] [PATCH 1/1] Ocfs2: Add new OCFS2_IOC_INFO ioctl for ocfs2 v7 Tristan Ye
2010-05-10 20:01 ` Joel Becker
2010-05-11  2:12   ` tristan
2010-05-11  6:51     ` Joel Becker [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-05-19  2:28 Tristan Ye
2010-05-20 23:26 ` Joel Becker
2010-05-20 23:49   ` Joel Becker
2010-05-21  9:07     ` tristan
2010-05-21 10:22       ` Joel Becker
2010-05-21  1:30   ` tristan
2010-05-21  2:41     ` Joel Becker
2010-05-21  3:05       ` tristan
2010-05-11  7:21 [Ocfs2-devel] [PATCH 0/1] Ocfs2: o2info for kernel v7 Tristan Ye
2010-05-11  7:21 ` [Ocfs2-devel] [PATCH 1/1] Ocfs2: Add new OCFS2_IOC_INFO ioctl for ocfs2 v7 Tristan Ye
2010-05-11 20:40   ` Joel Becker
2010-05-18 23:55     ` Joel Becker
2010-05-19  3:03       ` tristan
2010-04-26 12:17 Tristan Ye
2010-04-27 20:07 ` Sunil Mushran
2010-05-06  1:05 ` Joel Becker
2010-05-06  2:09   ` tristan
2010-04-19 11:00 Tristan Ye
2010-04-19 20:16 ` Sunil Mushran
2010-04-20  2:31   ` tristan
2010-04-20  4:28     ` Sunil Mushran

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=20100511065106.GA16757@mail.oracle.com \
    --to=joel.becker@oracle.com \
    --cc=ocfs2-devel@oss.oracle.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).