search for: unlocked

Hello - I'm trying to get Final Fantasy XI working under wine. In order to do that, I need to get the PlayOnline Viewer working first. According to the AppDB, PlayOnline was working up to Silver level on Wine 0.9.19. ( http://appdb.winehq.org/appview.php?iAppId=1992 ) I'm running FC6, Wine 0.9.30, and Nvidia drivers v1.0-9746. Below is the debug output that I get when trying to run the

Greetings, CentOS. After up2dating one of the corporate mail servers to CentOS 4.4 (was CentOS 4.2) and upgrading kernel to kernel-smp-2.6.9-42.0.3.EL, the following kernel messages started to appear in syslog: [root at gamma ~]# dmesg ........... ...CUT..... ........... lockd: unexpected unlock status: 1 lockd: unexpected unlock status: 1 lockd: unexpected unlock status: 1 lockd: unexpected

...ta > > structure. > > > > Linus suggested that we should not do any writes to lock after unlock(), > > and we can move slowpath clearing to fastpath lock. > > > > So this patch implements the fix with: > > 1. Moving slowpath flag to head (Oleg): > > Unlocked locks don't care about the slowpath flag; therefore we can keep > > it set after the last unlock, and clear it again on the first (try)lock. > > -- this removes the write after unlock. note that keeping slowpath flag would > > result in unnecessary kicks. > > By moving t...

...ta > > structure. > > > > Linus suggested that we should not do any writes to lock after unlock(), > > and we can move slowpath clearing to fastpath lock. > > > > So this patch implements the fix with: > > 1. Moving slowpath flag to head (Oleg): > > Unlocked locks don't care about the slowpath flag; therefore we can keep > > it set after the last unlock, and clear it again on the first (try)lock. > > -- this removes the write after unlock. note that keeping slowpath flag would > > result in unnecessary kicks. > > By moving t...

In the process of investigating a Cisco ATA 186 that was locked by Vonage, I found that you can still unlock the device yourself. But there's a catch. The device's design has a great plus: a DIP32 *socketed* SST28SF040A flash chip. I found an 8 digit unlock code at 0x03FA71-0x03FA78. I do not know if that is a standard location. If you have the equipment, you're in luck. But

...eBSD client (I tried the old nfs client and the new (mount_newnfs), not on a 2.6.32-358.11.1.el6.x86_64 CentOS release 6.4 (Final) Linux release. So my guess is that dovecot has some safety mechanism which tries to unlock locked files, maybe after some timeout and that, in the case of a an already unlocked file, the FreeBSD client sends the unlock RPC request to the server anyway whereas the linux client does not, noticing there isn't anything to unlock. Can you help me explaining such a behavior ? Are those "unlock a file with no prior lock" made on purpose or is it a bug ? Would it b...

...more. Exactly because a fast-path lock might come in, and release the whole data structure. Linus suggested that we should not do any writes to lock after unlock(), and we can move slowpath clearing to fastpath lock. So this patch implements the fix with: 1. Moving slowpath flag to head (Oleg): Unlocked locks don't care about the slowpath flag; therefore we can keep it set after the last unlock, and clear it again on the first (try)lock. -- this removes the write after unlock. note that keeping slowpath flag would result in unnecessary kicks. By moving the slowpath flag from the tail to the he...

...more. Exactly because a fast-path lock might come in, and release the whole data structure. Linus suggested that we should not do any writes to lock after unlock(), and we can move slowpath clearing to fastpath lock. So this patch implements the fix with: 1. Moving slowpath flag to head (Oleg): Unlocked locks don't care about the slowpath flag; therefore we can keep it set after the last unlock, and clear it again on the first (try)lock. -- this removes the write after unlock. note that keeping slowpath flag would result in unnecessary kicks. By moving the slowpath flag from the tail to the he...

Hi, I believe the following patch in the GIT - 2.6.17-rc5 is not correct: http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=75616cf9854b83eb83a968b1338ae0ee11c9673c It is the second of the two patches contributed by Leonid Ananiev. This one incorrectly adds the super block unlocking in the error path, though. As we can see in the function ext3_group_add() the

Hi, Environment: I am using CentOS 5.3 operating system. I upgraded xorg of centos to 7.3. I am using intel 945 GM board. My xorg server version is 1.4.2 and inetl driver version 2.4.3. gnome-screensaver version is 2.16.1-8.el5. Problem: I connected another system of same hardware using VGA output. Now I can see clone of my system on secondary display. I enabled screensaver with 1 minute period

R lets one lock an environment with both an R function, base::lockEnvironment, and a C function, R_LockEnvironment, but, as far as I can tell, no corresponding function to unlock an environment. Is this omission on principle or just something that has not been done yet? I ask because several packages, including the well-used R6 and rlang packages, fiddle with some bits in with SET_ENVFLAGS and

Hi, I have doubt in executing raw.write tests using lxc-execute. When I execute it without lxc-execute it works fine i.e it performs raw.write testing. command :: root at nishant:/home/nishant/Desktop/samba-4.0.0alpha15# bin/smbtorture //localhost/ubuntu -Ubase%base_system raw.write This command works fine. We can see the o/p of this also,

...gt; > > > Linus suggested that we should not do any writes to lock after unlock(), > > > and we can move slowpath clearing to fastpath lock. > > > > > > So this patch implements the fix with: > > > 1. Moving slowpath flag to head (Oleg): > > > Unlocked locks don't care about the slowpath flag; therefore we can keep > > > it set after the last unlock, and clear it again on the first (try)lock. > > > -- this removes the write after unlock. note that keeping slowpath flag would > > > result in unnecessary kicks. > &...

...gt; > > > Linus suggested that we should not do any writes to lock after unlock(), > > > and we can move slowpath clearing to fastpath lock. > > > > > > So this patch implements the fix with: > > > 1. Moving slowpath flag to head (Oleg): > > > Unlocked locks don't care about the slowpath flag; therefore we can keep > > > it set after the last unlock, and clear it again on the first (try)lock. > > > -- this removes the write after unlock. note that keeping slowpath flag would > > > result in unnecessary kicks. > &...

Odd problem here--I just got a couple of Cisco 7960s from Ebay that are not functioning as expected...... These 7960s can't seem to be unlocked for manual configuration via any mechanism that I can find. If you go to settings, there is no option 9 (unlock). Available options stop at 4 (Status). **# has no effect. The Phones report that thier current firmware version is 3.1 MF.G2. When plugged into a known good DHCP/TFTP server, t...

...ure. >>> >>> Linus suggested that we should not do any writes to lock after unlock(), >>> and we can move slowpath clearing to fastpath lock. >>> >>> So this patch implements the fix with: >>> 1. Moving slowpath flag to head (Oleg): >>> Unlocked locks don't care about the slowpath flag; therefore we can keep >>> it set after the last unlock, and clear it again on the first (try)lock. >>> -- this removes the write after unlock. note that keeping slowpath flag would >>> result in unnecessary kicks. >>>...

...ure. >>> >>> Linus suggested that we should not do any writes to lock after unlock(), >>> and we can move slowpath clearing to fastpath lock. >>> >>> So this patch implements the fix with: >>> 1. Moving slowpath flag to head (Oleg): >>> Unlocked locks don't care about the slowpath flag; therefore we can keep >>> it set after the last unlock, and clear it again on the first (try)lock. >>> -- this removes the write after unlock. note that keeping slowpath flag would >>> result in unnecessary kicks. >>>...

...nd inturn we can get rid of read/write after unlock (Oleg) - usage of ticket_equals (Oleg) Changes since V1: - Add missing TICKET_LOCK_INC before unlock kick (fixes hang in overcommit: Jeremy). - Remove SLOWPATH_FLAG clearing in fast lock. (Jeremy) - clear SLOWPATH_FLAG in arch_spin_value_unlocked during comparison. Note: The current implementation is still based on avoid writing after unlock. we could still have potential invalid memory read. (Sasha) Result: setup: 16core (32 cpu +ht sandy bridge 8GB 16vcpu guest) base = 3_19_rc7 3_19_rc7_spinfix_v3 +-----------+-----------+-------...

...nd inturn we can get rid of read/write after unlock (Oleg) - usage of ticket_equals (Oleg) Changes since V1: - Add missing TICKET_LOCK_INC before unlock kick (fixes hang in overcommit: Jeremy). - Remove SLOWPATH_FLAG clearing in fast lock. (Jeremy) - clear SLOWPATH_FLAG in arch_spin_value_unlocked during comparison. Note: The current implementation is still based on avoid writing after unlock. we could still have potential invalid memory read. (Sasha) Result: setup: 16core (32 cpu +ht sandy bridge 8GB 16vcpu guest) base = 3_19_rc7 3_19_rc7_spinfix_v3 +-----------+-----------+-------...

...might come in, and release the whole data > structure. > > Linus suggested that we should not do any writes to lock after unlock(), > and we can move slowpath clearing to fastpath lock. > > So this patch implements the fix with: > 1. Moving slowpath flag to head (Oleg): > Unlocked locks don't care about the slowpath flag; therefore we can keep > it set after the last unlock, and clear it again on the first (try)lock. > -- this removes the write after unlock. note that keeping slowpath flag would > result in unnecessary kicks. > By moving the slowpath flag fro...