public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Anand Jain <anand.jain@oracle.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: drop path before copying subvol info to userspace
Date: Tue, 8 Nov 2022 15:37:51 +0100	[thread overview]
Message-ID: <20221108143751.GA5824@twin.jikos.cz> (raw)
In-Reply-To: <3d46bd74955e2087332e492a96f6da78ca4ed533.1667898218.git.anand.jain@oracle.com>

On Tue, Nov 08, 2022 at 07:23:19PM +0530, Anand Jain wrote:
> Similar to the commit
>    btrfs: drop path before copying root refs to userspace
> 
> btrfs_ioctl_get_subvol_info() frees the search path after the userspace
> copy from the temp buffer %subvol_info. Fix this by freeing the path
> before we copy to userspace.

Seems that there are a few more ioctls that need to be fixed:
btrfs_ioctl_logical_to_ino,
btrfs_ioctl_ino_to_path,
btrfs_ioctl_get_subvol_rootref.

  reply	other threads:[~2022-11-08 14:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-08 13:53 [PATCH] btrfs: drop path before copying subvol info to userspace Anand Jain
2022-11-08 14:37 ` David Sterba [this message]
2022-11-10  6:06   ` 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=20221108143751.GA5824@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=anand.jain@oracle.com \
    --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