public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Adam Borowski <kilobyte@angband.pl>
To: linux-btrfs@vger.kernel.org
Subject: Bug#998840: Strange warning when deleting subvolume as non-root user
Date: Tue, 9 Nov 2021 03:52:24 +0100	[thread overview]
Message-ID: <YYniaHjEO9ssCiGq@angband.pl> (raw)

----- Forwarded message from Boris Kolpackov <boris@codesynthesis.com> -----
Date: Mon, 8 Nov 2021 16:01:53 +0200
From: Boris Kolpackov <boris@codesynthesis.com>
Subject: Bug#998840: Strange warning when deleting subvolume as non-root user

Package: btrfs-progs
Version: 5.14.1-1

After upgrading from btrfs-progs 5.7-1 with Linux kernel 5.7.6 to
btrfs-progs 5.14.1-1 with Linux kernel 5.14.9-2 (from current testing)
I see the following strange new warning when deleting the subvolume as
non-root user (the filesystem is mounted with user_subvol_rm_allowed):

WARNING: cannot read default subvolume id: Operation not permitted

The subvolume deletion succeeds.

To reproduce, mount a btrfs filesystem with user_subvol_rm_allowed,
say, on /mnt and then (assuming non-root user is called nonroot):

# chown nonroot:nonroot /mnt
# su - nonroot
$ cd /mnt
$ btrfs subvol create test
Create subvolume './test'
$ btrfs subvol delete test
WARNING: cannot read default subvolume id: Operation not permitted
Delete subvolume (no-commit): '/mnt/test'

Any idea what's going on here and how to get rid of this warning?
It adds quite a bit of noise to our logs.


----- End forwarded message -----


Reproduces for me both on 5.14 kernel+progs and 5.15.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Vat kind uf sufficiently advanced technology iz dis!?
⢿⡄⠘⠷⠚⠋⠀                                 -- Genghis Ht'rok'din
⠈⠳⣄⠀⠀⠀⠀

             reply	other threads:[~2021-11-09  2:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-09  2:52 Adam Borowski [this message]
2021-11-09 10:30 ` Bug#998840: Strange warning when deleting subvolume as non-root user Nikolay Borisov

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=YYniaHjEO9ssCiGq@angband.pl \
    --to=kilobyte@angband.pl \
    --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