Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: Julian Sikorski <belegdol@gmail.com>
To: Jeremy Allison <jra@samba.org>
Cc: linux-cifs@vger.kernel.org, Steve French <smfrench@gmail.com>
Subject: Re: Permission denied when chainbuilding packages with mock
Date: Mon, 8 Nov 2021 16:52:30 +0100	[thread overview]
Message-ID: <3c1d5ba0-74f6-d281-c50a-74046eb68708@gmail.com> (raw)
In-Reply-To: <cd649ed2-60d3-72e3-e09a-9f0074af99cc@gmail.com>

W dniu 08.11.2021 o 07:59, Julian Sikorski pisze:
> 
> 
> Am 08.11.21 um 02:48 schrieb Jeremy Allison:
>> On Sun, Nov 07, 2021 at 11:51:37PM +0100, Julian Sikorski wrote:
>>
>>> Thanks, this looks promising. Do you have any guesses as to why it 
>>> works for goffice-0.10.50-1.fc35 but not with goffice-0.10.50-2.fc35? 
>>> Race condition?
>>
>> No clue, sorry. I'd need to see comparative traces - but all that
>> will tell me is that it isn't doing the fsync on a read-only file.
> 
> I will try to generate a log for the working case later. Having said 
> that, the question becomes: why are some files read-only but others are 
> not, when they are generated by the same software in the same folder? 
> The permissions on both folders are exactly the same:
> 
> $ ls -l 
> /mnt/openmediavault/kernel/results/fedora-35-x86_64/goffice-0.10.50-2.fc35/
> 
> insgesamt 15360
> 
> -rwxr-xr-x. 1 julas julas  864488  7. Nov 23:53 build.log
> 
> -rwxr-xr-x. 1 julas julas 2443249  7. Nov 16:39 
> goffice-0.10.50-2.fc35.src.rpm
> 
> -rwxr-xr-x. 1 julas julas 2051776  7. Nov 16:39 
> goffice-0.10.50-2.fc35.x86_64.rpm
> 
> -rwxr-xr-x. 1 julas julas 2195483  7. Nov 16:39 
> goffice-debuginfo-0.10.50-2.fc35.x86_64.rpm
> 
> -rwxr-xr-x. 1 julas julas  967394  7. Nov 16:39 
> goffice-debugsource-0.10.50-2.fc35.x86_64.rpm
> 
> -rwxr-xr-x. 1 julas julas  339221  7. Nov 16:39 
> goffice-devel-0.10.50-2.fc35.x86_64.rpm
> 
> -rwxr-xr-x. 1 julas julas    3050  7. Nov 16:38 hw_info.log
> 
> -rwxr-xr-x. 1 julas julas   37268  7. Nov 16:38 installed_pkgs.log
> 
> drwxr-xr-x. 2 julas julas       0  7. Nov 16:39 repodata
> 
> -rwxr-xr-x. 1 julas julas  301702  7. Nov 23:53 root.log
> 
> -rwxr-xr-x. 1 julas julas    1710  7. Nov 23:53 state.log
> 
> -rwxr-xr-x. 1 julas julas       0  7. Nov 16:39 success
> 
> $ ls -l 
> /mnt/openmediavault/kernel/results/fedora-35-x86_64/goffice-0.10.50-1.fc35/
> 
> insgesamt 15360
> 
> -rwxr-xr-x. 1 julas julas  864469  7. Nov 16:34 build.log
> 
> -rwxr-xr-x. 1 julas julas 2443099  7. Nov 16:30 
> goffice-0.10.50-1.fc35.src.rpm
> 
> -rwxr-xr-x. 1 julas julas 2051631  7. Nov 16:30 
> goffice-0.10.50-1.fc35.x86_64.rpm
> 
> -rwxr-xr-x. 1 julas julas 2192839  7. Nov 16:30 
> goffice-debuginfo-0.10.50-1.fc35.x86_64.rpm
> 
> -rwxr-xr-x. 1 julas julas  967236  7. Nov 16:30 
> goffice-debugsource-0.10.50-1.fc35.x86_64.rpm
> 
> -rwxr-xr-x. 1 julas julas  339086  7. Nov 16:30 
> goffice-devel-0.10.50-1.fc35.x86_64.rpm
> 
> -rwxr-xr-x. 1 julas julas    3050  7. Nov 16:29 hw_info.log
> 
> -rwxr-xr-x. 1 julas julas   37268  7. Nov 16:29 installed_pkgs.log
> 
> drwxr-xr-x. 2 julas julas       0  7. Nov 16:30 repodata
> 
> -rwxr-xr-x. 1 julas julas  301199  7. Nov 16:34 root.log
> 
> -rwxr-xr-x. 1 julas julas    1665  7. Nov 16:34 state.log
> 
> -rwxr-xr-x. 1 julas julas       0  7. Nov 16:30 success
> 
> 
> The other explanation could be that the software (mock) runs fsync on 
> some of the files but not on others.
> 
> Best regards,
> Julian
I have now generated the logs from the working case:

https://www.dropbox.com/sh/9ucxoeia727xu3k/AABYiTQ0aBqCqnNL9Vz3Jch8a?dl=0

the moment at which failure would have happened is around 16:46:11.

Best regards,
Julian

  reply	other threads:[~2021-11-08 15:52 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-07 21:10 Permission denied when chainbuilding packages with mock Julian Sikorski
2021-11-07 21:44 ` Jeremy Allison
2021-11-07 21:49   ` Jeremy Allison
2021-11-07 22:03     ` Jeremy Allison
2021-11-07 22:15     ` Julian Sikorski
2021-11-07 22:47       ` Jeremy Allison
2021-11-07 22:50         ` Steve French
2021-11-07 22:55           ` Julian Sikorski
2021-11-08  1:46           ` Jeremy Allison
2021-11-07 22:51         ` Julian Sikorski
2021-11-08  1:48           ` Jeremy Allison
2021-11-08  6:59             ` Julian Sikorski
2021-11-08 15:52               ` Julian Sikorski [this message]
2021-11-08 16:46               ` Jeremy Allison
2021-11-09  8:10                 ` Steve French
2021-11-09  9:26                   ` Julian Sikorski
2021-11-10  0:54                     ` Jeremy Allison
2021-11-10  7:56                       ` Steve French
2021-11-10 11:23                         ` Julian Sikorski
2021-11-13 15:37                           ` Julian Sikorski
2021-11-15  3:25                             ` Steve French
2021-11-15  7:10                               ` Julian Sikorski
2021-11-09 19:25                   ` Jeremy Allison
  -- strict thread matches above, loose matches on Subject: below --
2021-11-07 15:44 Julian Sikorski

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=3c1d5ba0-74f6-d281-c50a-74046eb68708@gmail.com \
    --to=belegdol@gmail.com \
    --cc=jra@samba.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=smfrench@gmail.com \
    /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