Comment 8 for bug 314657

Thanks you, for your comment.
Happy to see that you are there to answer more questions.

Then, looking the backtrace, I remark:
#2 0x0000000000613c7b in smb_panic (why=<value optimized out>)
    at lib/util.c:1639
#3 0x0000000000618cf1 in assert_uid (ruid=4294967295, euid=10009)
    at lib/util_sec.c:102
#4 0x00000000004ba5ae in become_id (uid=10009, gid=1009) at smbd/sec_ctx.c:57
#5 0x00000000004ba726 in pop_sec_ctx () at smbd/sec_ctx.c:345
#6 0x00000000004afef9 in unbecome_root () at smbd/uid.c:400
#7 0x00000000005d3e31 in uid_to_sid (psid=0x7fffbddf39d0, uid=0)
    at passdb/lookup_sid.c:1169
#8 0x00000000004bfd3f in create_file_sids (psbuf=0x7fffbddf38f0,
    powner_sid=0x4d34, pgroup_sid=0x0) at smbd/posix_acls.c:668

Well, I am just a bug triager that does try to understand a bit more Linux.
It is unclear to me if ruid=4294967295 is supposed to be Root user, or who else.
Looks like it have try to be user with id=10009, but with the real id of 4294967295 (root?).
Which would seems ok, since it was called in the context of unbecome_root.

Anyway, in an bug #216358, Steve Langasek say:
"Hitting this assertion error should also generate log entries. Could you please check /var/log/samba/log.smbd (or the per-host logfile) for entries of the form "Failure to set uid privileges to [...]"? "

I guess, looking the said log file may give a hint.