From: David Sterba <dsterba@suse.cz>
To: Gerhard Heift <gerhard@heift.name>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: BTRFS_SEARCH_ARGS_BUFSIZE too small
Date: Thu, 16 Jan 2014 16:07:11 +0100 [thread overview]
Message-ID: <20140116150710.GL6498@suse.cz> (raw)
In-Reply-To: <CACeaM88ouFDe0WwYdaLq_8MFG4-UCH3rFowCLYbb3qaJCUcJaw@mail.gmail.com>
On Wed, Jan 15, 2014 at 08:29:22PM +0100, Gerhard Heift wrote:
> I have already patches for such an ioctl. Which form do you prefer?
Great!
> struct btrfs_ioctl_search_args_inline {
> struct btrfs_ioctl_search_key key;
> __u64 buf_len
> char buf[0];
> };
This one.
> char __user *buf;
We want to avoid dereferencing any user pointers in kernel, the whole
structure is one blob.
> And against which commit should I rebase them?
The kernel patches against btrfs-next, progs patches against any recent
integration branch.
david
prev parent reply other threads:[~2014-01-16 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 23:44 BTRFS_SEARCH_ARGS_BUFSIZE too small Gerhard Heift
2014-01-15 18:39 ` David Sterba
2014-01-15 19:29 ` Gerhard Heift
2014-01-16 15:07 ` David Sterba [this message]
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=20140116150710.GL6498@suse.cz \
--to=dsterba@suse.cz \
--cc=gerhard@heift.name \
--cc=linux-btrfs@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