reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: reiserfs-devel@vger.kernel.org
Subject: [Bug 207971] New: Wrong permissions with cp -a and reiserfs mounted with acl
Date: Fri, 29 May 2020 12:42:25 +0000	[thread overview]
Message-ID: <bug-207971-695@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 207971
           Summary: Wrong permissions with cp -a and reiserfs mounted with
                    acl
           Product: File System
           Version: 2.5
    Kernel Version: >=4.13.0
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: ReiserFS
          Assignee: reiserfs-devel@vger.kernel.org
          Reporter: marco@nucleus.it
        Regression: No

Copying files with the command
cp -a source destination
where destination is a filesystem with reiserfs format "3.6" with mount options
noatime,user_xattr,acl failed to preserve permissions.

I tested this behaviour with Ubuntu 16.04.6 LTS, Ubuntu 18.04.4 LTS and some
Gentoo custom installations.

Ubuntu kernel tested:
4.4.0-157-generic       ok
4.8.0-58-generic        ok
4.10.0-42-generic       ok
4.12.14-041214-generic  ok
4.13.0-45-generic       broken permissions
4.13.1-041301-generic   broken permissions
4.15.0-76-generic       broken permissions
4.15.0-101-generic      broken permissions
5.3.0-53-generic        broken permissions
5.6.14-050614-generic   broken permissions

Steps to reproduce the problem (you need lot of files and i used kernel
sources) and a device /dev/sdb formatted with reierfs:
apt-get install --no-install-recommends linux-source-4.15.0 
tar -jxf /usr/src/linux-source-4.15.0/linux-source-4.15.0.tar.bz2 -C /usr/src/
mkfs.reiserfs -f /dev/sdb
mount -o noatime,user_xattr,acl /dev/sdb /mnt
myk=/usr/src/linux-source-4.15.0
#Next command should return no files
find $myk -type f -perm 600
myt=/mnt/test2
#Copy the files
cp -a $myk $myt
#Next command should return some files
find $myt -type f -perm 600
#example of differences
tempfile=`find $myt -type f -perm 600 | head -n 1` 
ls -la ${myk}${tempfile#$myt} $tempfile

Example of broken permissions:
-rw------- 1 root root 67421 May 11 12:07 /mnt/test2/fs/nfs/dir.c
-rw-r--r-- 1 root root 67421 May 11 12:07
/usr/src/linux-source-4.15.0/fs/nfs/dir.c

Expected permissions:
-rw-r--r-- 1 root root 67421 May 11 12:07 /mnt/test2/fs/nfs/dir.c
-rw-r--r-- 1 root root 67421 May 11 12:07
/usr/src/linux-source-4.15.0/fs/nfs/dir.c

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2020-05-29 12:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-29 12:42 bugzilla-daemon [this message]
2020-05-29 12:43 ` [Bug 207971] Wrong permissions with cp -a and reiserfs mounted with acl bugzilla-daemon
2020-05-30  6:52 ` bugzilla-daemon
2021-10-08 15:41 ` bugzilla-daemon

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=bug-207971-695@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=reiserfs-devel@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;
as well as URLs for NNTP newsgroup(s).