search for: chunk_allocated

...&async->work); - wait_on_flush(root, info); + wait_on_flush(root, info, soft); return; flush: @@ -3146,14 +3152,17 @@ again: if (!delalloc_flushed) { delalloc_flushed = true; - flush_delalloc(root, meta_sinfo); + flush_delalloc(root, meta_sinfo, 1); goto again; } if (!chunk_allocated) { + int ret; + chunk_allocated = true; - btrfs_wait_ordered_extents(root, 0, 0); - maybe_allocate_chunk(root, meta_sinfo); + ret = maybe_allocate_chunk(root, meta_sinfo); + if (!ret) + flush_delalloc(root, meta_sinfo, 0); goto again; } @@ -3338,7 +3347,7 @@ again: if (!delallo...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 19 Nov 1999, Berend De Schouwer wrote: > RH6.0, Intel, openssh-1.2pre13 > > If I generate /etc/ssh_host_key, it works, if I generate > /root/.ssh/identity it segfaults. Every time. Fixed. There was a buffer overrun in the filename handling. Please try the attached patch. Regards, Damien Miller > # ssh-keygen >

Hi, I would like to report a bug in OpenSSH-1.2.2 (release) under Linux. Under certain conditions the sshd client process segfaults while doing the password authentification. I have observed the behaviour with glibc 2.0.7 (non-PAM), glibc 2.1.1 (PAM) and glibc 2.1.2 (PAM), when 'RhostsRSAAuthentication yes' is chosen in sshd_config. It appears to happen regardless whether PAM is used or

Hi! There is a situation when sshd will crash, but it might be rather hard to reproduce. I'll try to explain the setup :) S/KEY is compiled and installed (taken from http://www.sparc.spb.su/solaris/skey/ ) on Linux box (kernel 2.4.0). Then, OpenSSH 2.3.0p1 is compiled with skey support. It all works fine (patch has been applied too, which fixes skey issue found in November). Now, for the

----- Forwarded message from Telford Tendys <telford@triode.net.au> ----- Delivery-Date: Thu Jan 25 22:22:57 2001 Date: Fri, 26 Jan 2001 16:26:27 +1100 From: Telford Tendys <telford@triode.net.au> To: feedback@vorbis.com Subject: Comments on your code User-Agent: Mutt/1.2.5i Dear Vorbis, I didn't even know about ogg or vorbis until I was at a conference and someone said, ``if

I have had * installed for a couple of weeks now and am very impressed. I have got Zap, SIP and MGCP working and can call freely between them with just things like transfer still to sort out etc. I then though I would add H.323 support to my working system, having read the previous threads on the subject before I installed I installed the pre-reqs pwlib openh323 gnugk for h.323 gatekeeper