samba - Apr 2021 - Strange logs from smbd

Am 4/1/21 um 3:58 PM schrieb Ralph Boehme:
> Am 4/1/21 um 1:11 PM schrieb Roy Eastwood via samba:
>> I have a member server running in a LXD privileged container using a
>> btrfs storage pool for the container.?? I have been getting logs in
>> the form:
>>
>> Apr? 1 10:09:35 lxd-m1 smbd[4586]:?? btrfs_fget_compression: /proc
>> open of /proc/self/fd/50 failed: Permission denied
>>
>> Is this an artefact of running samba in a container and can these be
>> ignored or is it a problem I should be worried about??? Any advice
>> will be appreciated.
> 
> this is definitely something to worry about. I assume this is happening
> with Samba 4.14? That uses a new internal infrastructure code that makes
> use of re-opening fds via /proc/self/fd.
> 
> I've just checked and I don't see a problem inside a privileged
podmain
> container on kernel 5.10.22-200.fc33.x86_64 (latest Fedora).
fwiw, it seems the SYS_PTRACE cap is needed.

-slow

-- 
Ralph Boehme, Samba Team                https://samba.org/
Samba Developer, SerNet GmbH   https://sernet.de/en/samba/
GPG-Fingerprint   FAE2C6088A24252051C559E4AA1E9B7126399E46

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL:
<http://lists.samba.org/pipermail/samba/attachments/20210401/8ea1dc79/OpenPGP_signature.sig>

On 01 April 2021 15:01 Ralph Boehme wrote:
> Am 4/1/21 um 3:58 PM schrieb Ralph Boehme:
> > Am 4/1/21 um 1:11 PM schrieb Roy Eastwood via samba:
> >> I have a member server running in a LXD privileged container using
a
> >> btrfs storage pool for the container.   I have been getting logs
in
> >> the form:
> >>
> >> Apr  1 10:09:35 lxd-m1 smbd[4586]:   btrfs_fget_compression: /proc
> >> open of /proc/self/fd/50 failed: Permission denied
> >>
> >> Is this an artefact of running samba in a container and can these
be
> >> ignored or is it a problem I should be worried about?   Any advice
> >> will be appreciated.
> >
> > this is definitely something to worry about. I assume this is
happening
> > with Samba 4.14? That uses a new internal infrastructure code that
makes
> > use of re-opening fds via /proc/self/fd.
> >
> > I've just checked and I don't see a problem inside a
privileged podmain
> > container on kernel 5.10.22-200.fc33.x86_64 (latest Fedora).
> 
> fwiw, it seems the SYS_PTRACE cap is needed.
> 
> -slowcap
Yes, it's version 4.14.2.    I noticed it also with version 14.4.0 but today
had over 40 such logs which got my attention!

cap_sys_ptrace is enabled on the container.    Not familiar with ptrace though
so will need help if you need debug info.
Thanks.
Roy