search for: check_buffer

...ck test: write unlock time: 2011-11-10 18:37:03.372749 Inside RAW.WRITE (test_writeunlock)....and test_case name is :: write unlock Inside RAW.WRITE (test_writeunlock)....and test name is :: write unlock inside writeunlock Testing RAW_WRITE_WRITEUNLOCK Trying zero write Trying small write Inside check_buffer outside check_buffer Inside check_buffer outside check_buffer Trying large write Inside check_buffer outside check_buffer Trying bad fnum Setting file as sparse Trying 2^32 offset Inside check_buffer outside check_buffer outside writeunlock Inside file subunit.c and func subunit_test_name:: test_na...

...enbus/xenbus_comms.c Wed Oct 12 09:11:35 2005 +++ b/linux-2.6-xen-sparse/drivers/xen/xenbus/xenbus_comms.c Thu Oct 13 01:18:26 2005 @@ -130,7 +130,7 @@ wait_event_interruptible(xb_waitq, output_avail(out)); - mb(); + /* Make local copy of header to check for sanity. */ h = *out; if (!check_buffer(&h)) return -EIO; @@ -140,10 +140,20 @@ continue; if (avail > len) avail = len; + + /* Make sure we read header before we write data + * (implied by data-dependency, but let''s play safe). */ + mb(); + memcpy(dst, data, avail); data += avail; len -= avail;...

> you can't keep them in the main queue because you are subject to the > queue size cutoff so you either keep this within the per codec handle > structure (codec list) and/or in the block for the header pages (via the > associated pointer). The sending handlers are not really codec aware > but they do notice a change in headers. Yes, but that's the problem I'm facing:

...rtain things that could be done to help the situation, I'm not sure which would be best in your particular case but the current sync_point setting could be turned into a general bitmask flags, where sync point is just one and you can have codec specific allocations of those flags. Also the check_buffer routine is called before the send_to_listener. It's used to populate data from intro/fallback files or progress through the queue. You could set a special check buffer handler that checks the above refbuf_t flags. It's possible to create a per-client refbuf_t within there that hooks bac...

...signed int avail; + + get_output_chunk(out, out->buf, &avail); + return avail != 0; +} + static void update_output_chunk(struct ringbuf_head *h, uint32_t len) { h->write += len; @@ -99,10 +107,12 @@ void *data, unsigned int len) { unsigned int avail; + int was_full; if (!check_buffer(in)) barf("Corrupt buffer"); + was_full = !output_avail(in); while (len) { const void *src = get_input_chunk(in, in->buf, &avail); if (avail > len) @@ -114,7 +124,8 @@ } /* Tell other end we read something. */ - kill(daemon_pid, SIGUSR2); + if (was_full) + ki...