search for: smb_fname

...++ b/source3/modules/vfs_acl_common.c @@ -625,7 +625,7 @@ static NTSTATUS validate_nt_acl_blob(TALLOC_CTX *mem_ctx, vfs_handle_struct *handle, files_struct *fsp, const struct smb_filename *smb_fname, - DATA_BLOB *blob, + const DATA_BLOB *blob, struct security_descriptor **ppsd, bool *psd_is_from_fs) { Making the blob pointer parameter to validate_nt_...

On Fri, Aug 26, 2016 at 04:03:49PM -0700, Jeremy Allison wrote: > On Fri, Aug 26, 2016 at 02:46:19PM -0700, Jeremy Allison via samba wrote: > > On Fri, Aug 26, 2016 at 06:44:05PM +0200, Ralph Böhme wrote: > > > > > > Cheerio! > > > -slow > > > > Still reviewing this - but a few things that will need changing: > > > > When adding the

...t. Eg. validate_nt_acl_blob() has debug statements: 688 DEBUG(10, ("get_nt_acl_internal: ACL blob revision " 689 "mismatch (%u) for file %s\n", 690 (unsigned int)hash_type, 691 smb_fname->base_name)); 692 TALLOC_FREE(psd_blob); 693 return NT_STATUS_OK; 694 } 695 696 /* determine which type of xattr we got */ 697 if (hash_type != XATTR_SD_HASH_TYPE_SHA256) { 698 DEBUG(10, ("get_nt_acl_internal: A...

On Fri, Aug 26, 2016 at 06:33:26PM +0200, Ralph Böhme via samba wrote: > On Thu, Aug 25, 2016 at 12:14:00PM -0700, Jeremy Allison wrote: > > On Wed, Aug 24, 2016 at 04:06:42PM +0200, Ralph Böhme via samba wrote: > > > > > > Yeah, as much as I'd like to avoid adding a new option, I guess we > > > have to do something about it, my latest take on this is >

...ME_INFORMATION: + { + char *nfname = NULL; + + if (!fsp->conn->sconn->using_smb2) { + return NT_STATUS_INVALID_LEVEL; + } + + nfname = talloc_strdup(mem_ctx, smb_fname->base_name); + if (nfname == NULL) { + return NT_STATUS_NO_MEMORY; + } + + if (ISDOT(nfname)) { + nfname[0] = '\0'; + } +...

Upgraded to Samba 4.11.2 and I?ve now too started seeing the message: get_share_mode_lock: get_static_share_mode_data failed: NT_STATUS_NO_MEMORY A lot. I modified the source in source3/locking/share_mode_lock.c a bit in order to print out the values of the service path, smb_fname & old_write_time when it fails and it seems they are all NULL? [2019/11/14 14:24:23.358441, 0] ../../source3/locking/share_mode_lock.c:457(fresh_share_mode_lock) servicepath=0x0, smb_fname=0x0, old_write_time=0x0 [2019/11/14 14:24:23.358965, 1] ../../source3/locking/share_mode_lock.c:598(...

...security_info = 1, ppdesc = 0x0fffffffffffd378), line 1329 in "vfs_default.c" smb_vfs_call_get_nt_acl(handle = 0x0000000100104eac, name = "", security_info = 268435455, ppdesc = 0x09001000a00800b8), line 1754 in "vfs.c" smbd_check_open_rights(conn = 0x0000000110155aa0, smb_fname = 0x000000011015c290, access_mask = 16777216, access_granted = 0x0010008000100080), line 115 in "open.c" open_directory(conn = 0x0000000110155aa0, req = 0x000000011015c140, smb_dname = 0x000000011015c290, access_mask = 1048704, share_access = 0, create_disposition = 1, create_options = 83...

Hi all, On Thu, Apr 16, 2015 at 03:00:49PM -0700, Jeremy Allison wrote: > On Thu, Apr 16, 2015 at 08:42:48PM +0200, Ervin Heged?s wrote: > > Dear Samba users, > > > > here is an Ubuntu 14.04, with Samba 4 (4.1.6), and LDAP (slapd > > 2.4.31). The config came from a previous system (Debian Squeezy), > > which had been crashed (HW error - on this new machine,

...c5a894eb20, mem_ctx=0x7fc5a893aaa0) at ../source3/modules/vfs_acl_tdb.c:106 #9 acl_tdb_delete (db=db at entry=0x7fc5a894eb20, psbuf=psbuf at entry=0x7fc5a895df68, handle=0x7fc5a8945100) at ../source3/modules/vfs_acl_tdb.c:122 #10 0x00007fc58d962fe3 in unlink_acl_tdb (handle=0x7fc5a8945100, smb_fname=<optimized out>) at ../source3/modules/vfs_acl_tdb.c:269 #11 0x00007fc58d759802 in smb_full_audit_unlink (handle=0x7fc5a895c2c0, smb_fname=0x7fc5a896ed90) at ../source3/modules/vfs_full_audit.c:1333 #12 0x00007fc5a683540c in close_remove_share_mode (close_type=NORMAL_CLOSE, fsp=0x7fc5...

Hello all, after the upgarde from Samba 4.10.7 to 4.11.2 we get lots of these in our logfiles: 2019-11-28T20:40:44+01:00 lx-sv-09 smbd_audit: [2019/11/28 20:40:44.886615, 1] ../../source3/locking/share_mode_lock.c:597(get_share_mode_lock) 2019-11-28T20:40:44+01:00 lx-sv-09 smbd_audit: get_share_mode_lock: get_static_share_mode_data failed: NT_STATUS_NO_MEMORY There are no symptoms accept

...(!use_privs && get_current_uid(conn) == (uid_t)0) { /* I'm sorry sir, I didn't know you were root... */ DEBUG(10,("smbd_check_access_rights: root override " "on %s. Granting 0x%x\n", smb_fname_str_dbg(smb_fname), (unsigned int)access_mask )); return NT_STATUS_OK; } ... status = SMB_VFS_GET_NT_ACL(conn, smb_fname->base_name, (SECINFO_OWNER | SECINFO_GROUP | SECINFO_DACL), talloc_tos(), &sd); ?[2]? perf top call graph: ?1.49% libc-2...

...> at ../source3/modules/vfs_acl_tdb.c:106 > #9 acl_tdb_delete (db=db at entry=0x7fc5a894eb20, > psbuf=psbuf at entry=0x7fc5a895df68, > handle=0x7fc5a8945100) > at ../source3/modules/vfs_acl_tdb.c:122 > #10 0x00007fc58d962fe3 in unlink_acl_tdb (handle=0x7fc5a8945100, > smb_fname=<optimized out>) > at ../source3/modules/vfs_acl_tdb.c:269 > #11 0x00007fc58d759802 in smb_full_audit_unlink > (handle=0x7fc5a895c2c0, smb_fname=0x7fc5a896ed90) > at ../source3/modules/vfs_full_audit.c:1333 > #12 0x00007fc5a683540c in close_remove_share_mode > (close...

...amba 4.11.2 and I?ve now too started seeing the message: > > get_share_mode_lock: get_static_share_mode_data failed: > NT_STATUS_NO_MEMORY > > A lot. I modified the source in > source3/locking/share_mode_lock.c a bit in order to print out > the values of the service path, smb_fname & old_write_time > when it fails and it seems they are all NULL? > > > [2019/11/14 14:24:23.358441, 0] > ../../source3/locking/share_mode_lock.c:457(fresh_share_mode_lock) > servicepath=0x0, smb_fname=0x0, old_write_time=0x0 > [2019/11/14 14:24:23.358965, 1] > ....

...pgraded to Samba 4.11.2 and I?ve now too started seeing the message: > > get_share_mode_lock: get_static_share_mode_data failed: NT_STATUS_NO_MEMORY > > A lot. I modified the source in source3/locking/share_mode_lock.c a bit in > order to print out the values of the service path, smb_fname & > old_write_time when it fails and it seems they are all NULL? > > > [2019/11/14 14:24:23.358441, 0] > ../../source3/locking/share_mode_lock.c:457(fresh_share_mode_lock) > servicepath=0x0, smb_fname=0x0, old_write_time=0x0 > [2019/11/14 14:24:23.358965, 1] > ../../...

...dn't be, it isn't an error ;-) If you look at '/source3/locking/share_mode_lock.c' 'get_share_mode_lock' The relevant part is this: ??? ??? status = get_static_share_mode_data( ??? ??? ??? static_share_mode_record, ??? ??? ??? id, ??? ??? ??? servicepath, ??? ??? ??? smb_fname, ??? ??? ??? old_write_time); ??? ??? if (!NT_STATUS_IS_OK(status)) { ??? ??? ??? DBG_WARNING("get_static_share_mode_data failed: %s\n", ??? ??? ??? ??? ??? nt_errstr(status)); ??? ??? ??? goto fail; ??? ??? } It calls 'get_static_share_mode_data' and the relevant part of t...

...look at '/source3/locking/share_mode_lock.c' > 'get_share_mode_lock' > > The relevant part is this: > > ??? ??? status = get_static_share_mode_data( > ??? ??? ??? static_share_mode_record, > ??? ??? ??? id, > ??? ??? ??? servicepath, > ??? ??? ??? smb_fname, > ??? ??? ??? old_write_time); > ??? ??? if (!NT_STATUS_IS_OK(status)) { > ??? ??? ??? DBG_WARNING("get_static_share_mode_data failed: %s\n", > ??? ??? ??? ??? ??? nt_errstr(status)); > ??? ??? ??? goto fail; > ??? ??? } > > It calls 'get_static_share_m...

...2 s4slave smbd[7141]: smb_panic(): calling panic action [/bin/sleep 999999999] May 16 14:00:57 s4slave smbd[7173]: [2019/05/16 14:00:57.839574, 0] ../source3/smbd/dir.c:1440(user_can_write_file) May 16 14:00:57 s4slave smbd[7173]: PANIC: assert failed at ../source3/smbd/dir.c(1440): VALID_STAT(smb_fname->st) May 16 14:00:57 s4slave smbd[7173]: [2019/05/16 14:00:57.839682, 0] ../source3/lib/util.c:789(smb_panic_s3) May 16 14:00:57 s4slave smbd[7173]: PANIC (pid 7173): assert failed: VALID_STAT(smb_fname->st) May 16 14:00:57 s4slave smbd[7173]: [2019/05/16 14:00:57.840700, 0] ../source3/li...

Dear all, since a few days I have a panic error in my logfiles on my second joined DC, Samba version 4.3.4. Can anyone help? PANIC (pid 24120): assert failed: VALID_STAT(smb_fname->st) May 16 10:01:43 s4slave smbd[24120]: [2019/05/16 10:01:43.333006, 0] ../source3/lib/util.c:900(log_stack_trace) May 16 10:01:43 s4slave smbd[24120]: BACKTRACE: 30 stack frames: May 16 10:01:43 s4slave smbd[24120]: #0 /usr/local/samba/lib/libsmbconf.so.0(log_stack_trace+0x1f) [0x7f9cb9...

...ly fails then it would say "talloc failed" in fresh_share_mode_lock(). Can you check that for me? Assuming it doesn't say that, then the conditions for returning N_STATUS_NO_MEMORY from fresh_share_mode_lock() and so get_static_share_mode_data() are: if ((servicepath == NULL) || (smb_fname == NULL) || (old_write_time == NULL)) { return NULL; } None of these are memory related, confusingly. The full smb.conf Rowland asked for might help. Otherwise, if you are confident and if you have self-compiled this then if you can patch in a smb_panic() rather than the return NULL, an...

...started seeing the message: >> >> get_share_mode_lock: get_static_share_mode_data failed: >> NT_STATUS_NO_MEMORY >> >> A lot. I modified the source in >> source3/locking/share_mode_lock.c a bit in order to print out >> the values of the service path, smb_fname & old_write_time >> when it fails and it seems they are all NULL? >> >> >> [2019/11/14 14:24:23.358441, 0] >> ../../source3/locking/share_mode_lock.c:457(fresh_share_mode_lock) >> servicepath=0x0, smb_fname=0x0, old_write_time=0x0 >> [2019/11/14 1...