similar to: [klibc:master] fcntl: Fix file locking numbers for 64-bit architectures

Commit-ID: 11bd4ea5f3d960c4d208180deae91d88aa940149 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=11bd4ea5f3d960c4d208180deae91d88aa940149 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Mon, 21 Jan 2019 03:39:34 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Mon, 21 Jan 2019 03:45:04 +0000 [klibc] fcntl: Fix struct flock

Commit-ID: 3fefc6a404a970a911417d0345618a7e9abfef70 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=3fefc6a404a970a911417d0345618a7e9abfef70 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Wed, 6 Jan 2016 00:43:25 +0000 Committer: H. Peter Anvin <hpa at linux.intel.com> CommitDate: Tue, 5 Jan 2016 17:45:36 -0800 [klibc] MIPS: Update archfcntl.h

Here's an assortment of build and run-time fixes for various architectures that we've applied in Debian. Ben. Aurelien Jarno (1): ppc64: fix struct stat Ben Hutchings (2): MIPS: Update archfcntl.h syscalls: Override detection of direct socket syscalls on i386, m68k, s390 Helge Deller (1): Add pread and pwrite 32bit syscall wrappers for parisc Mauricio Faria de Oliveira

The parts of klibc specific to the mips architecture. Signed-off-by: H. Peter Anvin <hpa at zytor.com> --- commit 8dc79563c06020d8844b9e9b821741828039b59e tree b957c8fb1fddf486f5c26b1880726051d4f6aaad parent bc9b363b31d301ab94c115cccc2e079c0d318498 author H. Peter Anvin <hpa at zytor.com> Sun, 25 Jun 2006 16:58:31 -0700 committer H. Peter Anvin <hpa at zytor.com> Sun, 25 Jun

Commit-ID: 493f9a99220aed4eb7c6e3dd9018c037d45b13e2 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=493f9a99220aed4eb7c6e3dd9018c037d45b13e2 Author: Dejan Latinovic <Dejan.Latinovic at imgtec.com> AuthorDate: Thu, 5 Mar 2015 16:51:44 -0800 Committer: H. Peter Anvin <hpa at linux.intel.com> CommitDate: Thu, 5 Mar 2015 16:51:44 -0800 add-mips64-support-headers

Hi all, We've had a couple of incidents where Samba 2.2.5 on Solaris 8 has stopped accepting new connections...there are many smbd processes sitting there blocked doing a: fcntl(7, F_SETLKW64, 0xFFBED5E0) (sleeping...) We have around 400 users connecting on a daily basis. This message from Samba 2.2.3 days seems to suggest that there was a problem on Solaris with "fcntl locks with

On Tue, Sep 10, 2019 at 05:12:02PM +0200, Miklos Szeredi wrote: > I've folded the series from Vivek and fixed a couple of TODO comments > myself. AFAICS two issues remain that need to be resolved in the short > term, one way or the other: freeze/restore and full virtqueue. I have researched freeze/restore and come to the conclusion that it needs to be a future feature. It will

On Thu, Sep 12, 2019 at 10:14:11AM +0200, Miklos Szeredi wrote: > On Wed, Sep 11, 2019 at 5:54 PM Stefan Hajnoczi <stefanha at redhat.com> wrote: > > > > On Tue, Sep 10, 2019 at 05:12:02PM +0200, Miklos Szeredi wrote: > > > I've folded the series from Vivek and fixed a couple of TODO comments > > > myself. AFAICS two issues remain that need to be

On 11/08/2013 09:12 AM, Steve Capper wrote: > diff --git a/usr/klibc/open64.c b/usr/klibc/open64.c > new file mode 100644 > index 0000000..6ca603e > --- /dev/null > +++ b/usr/klibc/open64.c > @@ -0,0 +1,22 @@ > +/* > + * open64.c > + * > + * For 64 bit systems without the open syscall, pass straight > + * through into openat. > + */ > + > +#define

Hi, I am trying to understand file locking and share modes. I am using RedHat Enterprise Linux 4, with kernel 2.6.9-55.ELsmp, samba-3.0.10-1.4E.11 and Windows XP. In particular I am looking at a machine running Linux exporting its local filesystem using Samba, with a Windows client accessing the file share. If I use byte range locking (fcntl() on Linux, LockFile() on Windows) things work as

Commit-ID: 8858e8319655ef38398e0833b71d65b0e620a061 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=8858e8319655ef38398e0833b71d65b0e620a061 Author: Steve Capper <steve.capper at linaro.org> AuthorDate: Mon, 11 Nov 2013 17:04:11 +0000 Committer: H. Peter Anvin <hpa at zytor.com> CommitDate: Mon, 11 Nov 2013 19:31:13 -0800 [klibc] syscalls: Add syscalls

Hi, this is an old problem it was worse in the pre-3.5.0 releases, on solaris 10 all the cpu gets consumed by fcntl calls: 7963: fcntl(22, F_SETLKW64, 0xFFBFE050) = 0 7963: fcntl(22, F_SETLKW64, 0xFFBFDE78) = 0 7963: fcntl(22, F_SETLKW64, 0xFFBFDF58) = 0 7963: fcntl(22, F_SETLKW64, 0xFFBFDF70) = 0 7963: fcntl(22, F_SETLKW64,

Hi, I am still struggling with the printing in a AD2008 R2 environment I changed to 3.2.15 by now. Still very slow, I am running on solaris 10. Not sure if my clients are so chatty by now but it is really killing any performance. Using truss I see loads of: 19702: fcntl(17, F_SETLKW64, 0xFFBFE640) = 0 19702: fcntl(17, F_SETLKW64, 0xFFBFE150) = 0 19702: fcntl(17,

An old problem has started to reappear with our Solaris (2.8) Samba (3.0.23b). This was after an upgrade from 3.0.22 in which the problem was worse. Occasionally an smbd process will go "rogue" and start consuming CPU cycles until killed. I did a truss of the process and got back this tight loop. fcntl(27, F_SETLKW64, 0xFFBEEF98) = 0 fcntl(27, F_SETLKW64, 0xFFBEF010)

Anybody? 2017. 05. 02. 10:48 keltezéssel, Papp Bence via samba írta: > Hi! > > > I need some help. > > We use samba4 as AD, and now when clients connect to server, samba > process stuck at 100% cpu. > > samba Version: 4.3.4 Release: 13.el6 > > > top: > > 3777 root 20 0 131m 46m 28m R 99.7 0.3 219:20.53 > /usr/local/samba4//sbin/samba -D

Here is the smb.conf: https://pastebin.com/LUf4MUF0 Thank you very much. 2017. 05. 09. 18:15 keltezéssel, Dante F. B. Colò via samba írta: > Did you install it from binary packages ? compiled from source ? Post your smb.conf here. > > > ----- Original Message ----- > From: "samba" <samba at lists.samba.org> > To: "samba" <samba at

Did you install it from binary packages ? compiled from source ? Post your smb.conf here. ----- Original Message ----- From: "samba" <samba at lists.samba.org> To: "samba" <samba at lists.samba.org> Sent: Tuesday, May 9, 2017 1:01:10 PM Subject: Re: [Samba] samba process use 100% cpu Anybody? 2017. 05. 02. 10:48 keltezéssel, Papp Bence via samba írta: > Hi!

I have a reproducible intermittent error large site - "The specified network name is no longer available". This happens when copying large files. Below is part of log level 10 output & strace. Sorry for the long posting. I will probably need to put the loglevel 10 attached to a bugzilla - but thought I would try the lists initially. RHEL4 samba-3.0.25b-1.el4_6.4

Hi! I need some help. We use samba4 as AD, and now when clients connect to server, samba process stuck at 100% cpu. samba Version: 4.3.4 Release: 13.el6 top: 3777 root 20 0 131m 46m 28m R 99.7 0.3 219:20.53 /usr/local/samba4//sbin/samba -D 24541 csertam 20 0 49260 11m 9048 S 25.1 0.1 0:01.56 smbd -D 7080 squid 20 0 926m 908m 6428 S 9.9 6.2 11:43.50

The latest version that Western Digital has shipped with the My cloud devices accesses the disk about twice a minute. The access to /dev/sda2 is causing the system to keep the disk from going into standby mode. I don't understand the call to quotactl every minute when no one is trying to access the share. An strace of one of the processes shows the following: poll([{fd=13,