search for: nentry

ttm_bo_delayed_delete has a race condition, because after we do: kref_put(&nentry->list_kref, ttm_bo_release_list); we are not holding the list lock and not holding any reference to objects, and thus every bo in the list can be removed and freed at this point. However, we then use the next pointer we stored, which is not guaranteed to be valid. This was apparently the caus...

ttm_bo_delayed_delete has a race condition, because after we do: kref_put(&nentry->list_kref, ttm_bo_release_list); we are not holding the list lock and not holding any reference to objects, and thus every bo in the list can be removed and freed at this point. However, we then use the next pointer we stored, which is not guaranteed to be valid. This was apparently the caus...

Resending this with Thomas Hellstrom's signoff for merging into 2.6.33 ttm_bo_delayed_delete has a race condition, because after we do: kref_put(&nentry->list_kref, ttm_bo_release_list); we are not holding the list lock and not holding any reference to objects, and thus every bo in the list can be removed and freed at this point. However, we then use the next pointer we stored, which is not guaranteed to be valid. This was apparently the caus...

Hi, I'm having an issue trying to make a Windows machine sambaserveroin a Samba domain. Samba is running with LDAP backend (OpenLDAP). When I try to join the domain, Windows says that the machine account does not exist. The machine account, however, is successfully created in the LDAP directory after the join fails. When I try to join again, Windows says that the account already exists.

Hi Harry, sadmin and tadmin are both admin logins. I was trying to domain join with both. sadmin is in ldap The olcdbindex.ldif gave this error SASL/EXTERNAL authentication started SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth SASL SSF: 0 modifying entry "olcDatabase={1}hdb,cn=config" ldap_modify: Other (e.g., implementation specific) error (80) additional

Add functions implementing MSI-X support. First user will be virtio-pci. Note that platform must set a flag to declare MSI supported. For PC this will be set by APIC. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- Makefile.target | 2 +- hw/msix.c | 423 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ hw/msix.h | 35 +++++ hw/pci.h | 20 +++ 4

Add functions implementing MSI-X support. First user will be virtio-pci. Note that platform must set a flag to declare MSI supported. For PC this will be set by APIC. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- Makefile.target | 2 +- hw/msix.c | 423 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ hw/msix.h | 35 +++++ hw/pci.h | 20 +++ 4

Hi, I have a LDAP backend for my Samba 3.0.2, and everything seems to work except adding XP machines to the domain, and unix logins with a ldap client. Since this mail is very long, I have created a small index, so you don't get exhaustet in the middle of all the logs... ;) 1. LDAP user-creation 2. Group info 3. pam/nss info 4. smb.conf [global] 5. Log from trying to add machine to

Hi, I have managed to configure Samba+LDAP+smbldap-tools. Everything works fine, except one strange problem is appearing. When I connect with Windows tool UserManagerForDomains or I want to create a share on a Wndows box I can see the users but no groups. With UserManagerForDomains is see following: Users: All the users Groups: none, just description of Replicators Group and the

Add functions implementing MSI-X support. First user will be virtio-pci. Note that platform must set a flag to declare MSI supported. For PC this will be set by APIC. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- Makefile.target | 2 +- hw/msix.c | 423 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ hw/msix.h | 35 +++++ hw/pci.h | 20 +++ 4

Add functions implementing MSI-X support. First user will be virtio-pci. Note that platform must set a flag to declare MSI supported. For PC this will be set by APIC. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- Makefile.target | 2 +- hw/msix.c | 423 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ hw/msix.h | 35 +++++ hw/pci.h | 20 +++ 4

Add functions implementing MSI-X support. First user will be virtio-pci. Note that platform must set a flag to declare MSI supported: this is a safety measure to avoid breaking platforms which should support MSI-X but currently lack this in the interrupt controller emulation. For PC this will be set by APIC. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- Makefile.target | 2

Add functions implementing MSI-X support. First user will be virtio-pci. Note that platform must set a flag to declare MSI supported: this is a safety measure to avoid breaking platforms which should support MSI-X but currently lack this in the interrupt controller emulation. For PC this will be set by APIC. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- Makefile.target | 2

Add functions implementing MSI-X support. First user will be virtio-pci. Note that platform must set a flag to declare MSI supported: this is a safety measure to avoid breaking platforms which should support MSI-X but currently lack this in the interrupt controller emulation. For PC this will be set by APIC. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- Makefile.target | 2

Add functions implementing MSI-X support. First user will be virtio-pci. Note that platform must set a flag to declare MSI supported: this is a safety measure to avoid breaking platforms which should support MSI-X but currently lack this in the interrupt controller emulation. For PC this will be set by APIC. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- Makefile.target | 2

Add functions implementing MSI-X support. First user will be virtio-pci. Note that platform must set a flag to declare MSI supported. For PC this will be set by APIC. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- Makefile.target | 2 +- hw/msix.c | 423 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ hw/msix.h | 35 +++++ hw/pci.h | 20 +++ 4

Add functions implementing MSI-X support. First user will be virtio-pci. Note that platform must set a flag to declare MSI supported. For PC this will be set by APIC. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- Makefile.target | 2 +- hw/msix.c | 423 +++++++++++++++++++++++++++++++++++++++++++++++++++++++ hw/msix.h | 35 +++++ hw/pci.h | 20 +++ 4

Hi Harry, Here are the outputs. I've attached them as logs with this email too. root at sam3dc:/tmp/ldifs-gr# ldapmodify -Y external -H ldapi:/// -f olcdbindex.ldif SASL/EXTERNAL authentication started SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth SASL SSF: 0 modifying entry "olcDatabase={1}hdb,cn=config" root at sam3dc:/tmp/ldifs-gr# service slapd stop

Hi there! To set up a samba PDC with openLDAP on my openSUSE 10.1 x86_64 I followed this howto: http://en.opensuse.org/Howto_setup_SUSE_10.1_as_Samba_PDC Every service seems to be running now but now I'm stuck. I was able to join a clean Windows XP Pro test machine to my Domain and I'm able to log on as normal LDAP user. The home-share is mounted and even a login script (actually just

Using Samba 3.0.2pre1 under SuSE 8.2. I have seen several references now in this list noting that the browse for machine accounts in Samba 3 is broken, and 'People' should be used instead. I changed smb.conf to 'ldp machine suffix = ou=People' and I changed smbldap_conf.pm to '$computersou=(People). I then cleared ldap, ran smbldap-populate.pl, and changed the uid of