ocfs2-devel.oss.oracle.com archive mirror
 help / color / mirror / Atom feed
From: tristan <tristan.ye@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: Wed, 19 May 2010 11:03:09 +0800	[thread overview]
Message-ID: <4BF354ED.3090603@oracle.com> (raw)
In-Reply-To: <20100518235505.GP3239@mail.oracle.com>

Joel Becker wrote:
> On Tue, May 11, 2010 at 01:40:35PM -0700, Joel Becker wrote:
>   
>> On Tue, May 11, 2010 at 03:21:49PM +0800, Tristan Ye wrote:
>>     
>>> +/*
>>> + * This call is void because we are already reporting an error that may
>>> + * be -EFAULT.  The error will be returned from the ioctl(2) call.  It's
>>> + * just a best-effort to tell userspace that this request caused the error.
>>> + */
>>> +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)put_user(kreq->ir_flags, (__u32 __user *)&(req->ir_flags));
>>> +}
>>> +
>>> +#define o2info_error_to_user(a, b) \
>>> +		__o2info_error_to_user((struct ocfs2_info_request *)&(a), b)
>>>       
>> 	Hmm, since we're not actually passing the error up, perhaps it
>> should be called "[__]o2info_set_request_error(a, b)".
>>     
>
> Can you make this change so I can push this to .35?
>   

Sent out.

> Joel
>
>   

  reply	other threads:[~2010-05-19  3:03 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [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-06  8:43 Tristan Ye
2010-05-10 20:01 ` Joel Becker
2010-05-11  2:12   ` tristan
2010-05-11  6:51     ` Joel Becker
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=4BF354ED.3090603@oracle.com \
    --to=tristan.ye@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).