From: Anand Jain <Anand.Jain@oracle.com>
To: Stefan Behrens <sbehrens@giantdisaster.de>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: device delete to get errors from the kernel
Date: Tue, 30 Apr 2013 14:14:48 +0800 [thread overview]
Message-ID: <517F6158.5000405@oracle.com> (raw)
In-Reply-To: <517A5C27.3090803@giantdisaster.de>
Thanks Stefan.
::
> About the issue you mentioned, that you need to change the kernel and
> the user mode at the same time:
> You can keep it compatible. Just do not delete the old kernel interface.
> The user mode program could try the new interface first, and if it
> fails, fall back to the old interface. You can use the same ioctl number
> for both ways if you change the length of the ioctl parameter.
Here there won't be a definite failure as such,
kernel could send or read garbage if the old and
new structures don't match.
The problem with most of the ioctl api structures
are they don't (already) share the struct len. So
it won't be possible to know which version of the
structure is being used by the other party?
Anand
next prev parent reply other threads:[~2013-04-30 6:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 3:39 [bug] error communication from kernel to userland Anand Jain
2013-04-26 9:39 ` device delete to get errors from the kernel Anand Jain
2013-04-26 9:41 ` [PATCH] btrfs-progs: " Anand Jain
2013-04-26 9:41 ` [PATCH] btrfs: " Anand Jain
2013-04-29 19:12 ` Josef Bacik
2013-04-30 5:55 ` Anand Jain
2013-04-26 10:51 ` Stefan Behrens
2013-04-30 6:14 ` Anand Jain [this message]
2013-04-30 13:17 ` Anand Jain
2013-04-30 13:19 ` [PATCH v2] btrfs: " Anand Jain
2013-04-30 13:19 ` [PATCH v2] btrfs-progs: " Anand Jain
2013-05-17 10:53 ` [PATCH v3] " Anand Jain
2013-05-06 19:39 ` [PATCH v2] btrfs: " Josef Bacik
2013-05-17 10:52 ` [PATCH v3] " Anand Jain
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=517F6158.5000405@oracle.com \
--to=anand.jain@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sbehrens@giantdisaster.de \
/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