linux-ext4 - [Bug 70831] New: Bind mount doesn't allow to trash files and directories

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <bug-70831-13602@https.bugzilla.kernel.org/>
Date:	Wed, 19 Feb 2014 11:02:43 +0000
From:	bugzilla-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 70831] New: Bind mount doesn't allow to trash files and
 directories

https://bugzilla.kernel.org/show_bug.cgi?id=70831

            Bug ID: 70831
           Summary: Bind mount doesn't allow to trash files and
                    directories
           Product: File System
           Version: 2.5
    Kernel Version: Debian 3.11.8-1
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: ext4
          Assignee: fs_ext4@...nel-bugs.osdl.org
          Reporter: dbz.gml@...il.com
        Regression: No

Hello.

I've asked a question here
(https://unix.stackexchange.com/questions/115757/bind-mount-unable-to-delete-files-to-trash)
about strange situation with deleting files from bind-mounted directories.
Someone Ricky Beam supposed this is a kernel issue.

This is a quote of his words:
[QUOTE]
This is a linux kernel issue. It's not looking at the true super-block of the
source and destination filesystems:

17926 rename("d1/foo", "d2/foo")        = -1 EXDEV (Invalid cross-device link)
Looks like the issue is in do_rename() (fs/namei.c):

    error = -EXDEV;
    if (oldnd.mnt != newnd.mnt)
            goto exit2;
*sigh*
[/QUOTE]

Could you please take a look at this issue and confirm or disprove this is a
kernel issue?
Thank you very much!

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html