.. Copyright (c) 2010-2021 Varnish Software AS SPDX-License-Identifier: BSD-2-Clause See LICENSE file for full text of license .. _ref-vmod: %%%%%%%%%%%%%%%%%%%%%% VMOD - Varnish Modules %%%%%%%%%%%%%%%%%%%%%% For all you can do in VCL, there are things you cannot do. Look an IP number up in a database file for instance. VCL provides for inline C code, and there you can do everything, but it is not a convenient or even readable way to solve such problems. This is where VMODs come into the picture: A VMOD is a shared library with some C functions which can be called from VCL code. For instance:: import std; sub vcl_deliver { set resp.http.foo = std.toupper(req.url); } The "std" vmod is one you get with Varnish, it will always be there and we will put "boutique" functions in it, such as the "toupper" function shown above. The full contents of the "std" module is documented in vmod_std(3). This part of the manual is about how you go about writing your own VMOD, how the language interface between C and VCC works, where you can find contributed VMODs etc. This explanation will use the "std" VMOD as example, having a Varnish source tree handy may be a good idea. VMOD Directory ============== The VMOD directory is an up-to-date compilation of maintained extensions written for Varnish Cache: https://www.varnish-cache.org/vmods The vmod.vcc file ================= The interface between your VMOD and the VCL compiler ("VCC") and the VCL runtime ("VRT") is defined in the vmod.vcc file which a python script called "vmodtool.py" turns into thaumaturgically challenged C data structures that do all the hard work. The std VMODs vmod.vcc file looks somewhat like this:: $ABI strict $Version my.version $Module std 3 "Varnish Standard Module" $Event event_function $Function STRING toupper(STRANDS s) $Function STRING tolower(STRANDS s) $Function VOID set_ip_tos(INT) The ``$ABI`` line is optional. Possible values are ``strict`` (default) and ``vrt``. It allows to specify that a vmod is integrating with the blessed ``vrt`` interface provided by ``varnishd`` or go deeper in the stack. As a rule of thumb you, if the VMOD uses more than the VRT (Varnish RunTime), in which case it needs to be built for the exact Varnish version, use ``strict``. If it complies to the VRT and only needs to be rebuilt when breaking changes are introduced to the VRT API, use ``vrt``. The ``$Version`` line is also optional. It specifies the version identifier compiled into the VMOD binary for later identification. If omitted, ``PACKAGE_STRING`` from an automake ``Makefile`` will be used, or ``NOVERSION`` otherwise. The ``$Module`` line gives the name of the module, the manual section where the documentation will reside, and the description. The ``$Event`` line specifies an optional "Event" function, which will be called whenever a VCL program which imports this VMOD is loaded or transitions to any of the warm, active, cold or discarded states. More on this below. The ``$Function`` lines define three functions in the VMOD, along with the types of the arguments, and that is probably where the hardest bit of writing a VMOD is to be found, so we will talk about that at length in a moment. Notice that the third function returns VOID, that makes it a "procedure" in VCL lingo, meaning that it cannot be used in expressions, right side of assignments and such. Instead it can be used as a primary action, something functions which return a value cannot:: sub vcl_recv { std.set_ip_tos(32); } Running vmodtool.py on the vmod.vcc file, produces a "vcc_if.c" and "vcc_if.h" files, which you must use to build your shared library file. Forget about vcc_if.c everywhere but your Makefile, you will never need to care about its contents, and you should certainly never modify it, that voids your warranty instantly. But vcc_if.h is important for you, it contains the prototypes for the functions you want to export to VCL. For the std VMOD, the compiled vcc_if.h file looks like this:: VCL_STRING vmod_toupper(VRT_CTX, VCL_STRANDS); VCL_STRING vmod_tolower(VRT_CTX, VCL_STRANDS); VCL_VOID vmod_set_ip_tos(VRT_CTX, VCL_INT); vmod_event_f event_function; Those are your C prototypes. Notice the ``vmod_`` prefix on the function names, more on that in :ref:`ref-vmod-symbols`. Named arguments and default values ---------------------------------- The basic vmod.vcc function declaration syntax introduced above makes all arguments mandatory for calls from vcl - which implies that they need to be given in order. Naming the arguments as in:: $Function BOOL match_acl(ACL acl, IP ip) allows calls from VCL with named arguments in any order, for example:: if (debug.match_acl(ip=client.ip, acl=local)) { # ... Named arguments also take default values, so for this example from the debug vmod:: $Function STRING argtest(STRING one, REAL two=2, STRING three="3", STRING comma=",", INT four=4) only argument `one` is required, so that all of the following are valid invocations from vcl:: debug.argtest("1", 2.1, "3a") debug.argtest("1", two=2.2, three="3b") debug.argtest("1", three="3c", two=2.3) debug.argtest("1", 2.4, three="3d") debug.argtest("1", 2.5) debug.argtest("1", four=6); The C interface does not change with named arguments and default values, arguments remain positional and default values appear no different to user specified values. `Note` that default values have to be given in the native C-type syntax, see below. As a special case, ``NULL`` has to be given as ``0``. Optional arguments ------------------ The vmod.vcc declaration also allows for optional arguments in square brackets like so:: $Function VOID opt(PRIV_TASK priv, INT four = 4, [STRING opt]) With any optional argument present, the C function prototype looks completely different: * Only the ``VRT_CTX`` and object pointer arguments (only for methods) remain positional * All other arguments get passed in a struct as the last argument of the C function. The argument struct is simple, vmod authors should check the `vmodtool`-generated ``vcc_if.c`` file for the function and struct declarations: * for each optional argument, a ``valid_``\ `argument` member is used to signal the presence of the respective optional argument. ``valid_`` argstruct members should only be used as truth values, irrespective of their actual data type. * named arguments are passed in argument struct members by the same name and with the same data type. * unnamed (positional) arguments are passed as ``arg``\ `n` with `n` starting at 1 and incrementing with the argument's position. Optionally, the VCL and C argument names can be specified independently using the ``:`` syntax. See :ref:`ref-vmod-symbols` for details. .. _ref-vmod-vcl-c-objects: Objects and methods ------------------- Varnish also supports a simple object model for vmods. Objects and methods are declared in the vcc file as:: $Object class(...) $Method .method(...) For declared object classes of a vmod, object instances can then be created in ``vcl_init { }`` using the ``new`` statement:: sub vcl_init { new foo = vmod.class(...); } and have their methods called anywhere (including in ``vcl_init {}`` after the instantiation):: sub somewhere { foo.method(...); } Nothing prevents a method to be named like the constructor and the meaning of such a method is up to the vmod author:: $Object foo(...) $Method .bar(...) $Method .foo(...) Object instances are represented as pointers to vmod-implemented C structs. Varnish only provides space to store the address of object instances and ensures that the right object address gets passed to C functions implementing methods. * Objects' scope and lifetime are the vcl * Objects can only be created in ``vcl_init {}`` and have their destructors called by varnish after ``vcl_fini {}`` has completed. vmod authors are advised to understand the prototypes in the `vmodtool`\ -generated ``vcc_if.c`` file: * For ``$Object`` declarations, a constructor and destructor function must be implemented * The constructor is named by the suffix ``__init``, always is of ``VOID`` return type and has the following arguments before the vcc-declared parameters: * ``VRT_CTX`` as usual * a pointer-pointer to return the address of the created oject * a string containing the vcl name of the object instance * The destructor is named by the suffix ``__fini``, always is of ``VOID`` return type and has a single argument, the pointer-pointer to the address of the object. The destructor is expected clear the address of the object stored in that pointer-pointer. * Methods gain the pointer to the object as an argument after the ``VRT_CTX``. As varnish is in no way involved in managing object instances other than passing their addresses, vmods need to implement all aspects of managing instances, in particular their memory management. As the lifetime of object instances is the vcl, they will usually be allocated from the heap. Functions and Methods scope restriction --------------------------------------- The ``$Restrict`` stanza offers a way to limit the scope of the preceding vmod function or method, so that they can only be called from restricted vcl call sites. It must only appear after a ``$Method`` or ``$Function`` and has the following syntax:: $Restrict scope1 [scope2 ...] Possible scope values are: ``backend, client, housekeeping, vcl_recv, vcl_pipe, vcl_pass, vcl_hash, vcl_purge, vcl_miss, vcl_hit, vcl_deliver, vcl_synth, vcl_backend_fetch, vcl_backend_response, vcl_backend_error, vcl_init, vcl_fini`` Deprecated Aliases ------------------ The ``$Alias`` stanza offers a mechanism to rename a function or an object's method without removing the previous name. This allows name changes to maintain compatibility until the alias is dropped. The syntax for a function is:: $Alias deprecated_function original_function [description] The syntax for a method is:: $Alias .deprecated_method object.original_method [description] The ``$Alias`` stanza can appear anywhere, this allows grouping them in a dedicated "deprecated" section of their manual. The optional description can be used to explain why a function was renamed. .. _ref-vmod-vcl-c-types: VCL and C data types ==================== VCL data types are targeted at the job, so for instance, we have data types like "DURATION" and "HEADER", but they all have some kind of C language representation. Here is a description of them. All but the PRIV types have typedefs: VCL_INT, VCL_REAL, etc. Notice that most of the non-native (C pointer) types are ``const``, which, if returned by a vmod function/method, are assumed to be immutable. In other words, a vmod `must not` modify any data which was previously returned. When returning non-native values, the producing function is responsible for arranging memory management. Either by freeing the structure later by whatever means available or by using storage allocated from the client or backend workspaces. ACL C-type: ``const struct vrt_acl *`` A type for named ACLs declared in VCL. BACKEND C-type: ``const struct director *`` A type for backend and director implementations. See :ref:`ref-writing-a-director`. BLOB C-type: ``const struct vmod_priv *`` An opaque type to pass random bits of memory between VMOD functions. BODY C-type: ``const void *`` A type only used on the LHS of an assignment that can take either a blob or an expression that can be converted to a string. BOOL C-type: ``unsigned`` Zero means false, anything else means true. BYTES C-type: ``double`` Unit: bytes. A storage space, as in 1024 bytes. DURATION C-type: ``double`` Unit: seconds. A time interval, as in 25 seconds. ENUM vcc syntax: ENUM { val1, val2, ... } vcc example: ``ENUM { one, two, three } number="one"`` C-type: ``const char *`` Allows values from a set of constant strings. `Note` that the C-type is a string, not a C enum. Enums will be passed as fixed pointers, so instead of string comparisons, also pointer comparisons with ``VENUM(name)`` are possible. HEADER C-type: ``const struct gethdr_s *`` These are VCL compiler generated constants referencing a particular header in a particular HTTP entity, for instance ``req.http.cookie`` or ``beresp.http.last-modified``. By passing a reference to the header, the VMOD code can both read and write the header in question. If the header was passed as STRING, the VMOD code only sees the value, but not where it came from. HTTP C-type: ``struct http *`` A reference to a header object as ``req.http`` or ``bereq.http``. INT C-type: ``long`` A (long) integer as we know and love them. IP C-type: ``const struct suckaddr *`` This is an opaque type, see the ``include/vsa.h`` file for which primitives we support on this type. PRIV_CALL See :ref:`ref-vmod-private-pointers` below. PRIV_TASK See :ref:`ref-vmod-private-pointers` below. PRIV_TOP See :ref:`ref-vmod-private-pointers` below. PRIV_VCL See :ref:`ref-vmod-private-pointers` below. PROBE C-type: ``const struct vrt_backend_probe *`` A named standalone backend probe definition. REAL C-type: ``double`` A floating point value. REGEX C-type: ``const struct vre *`` This is an opaque type for regular expressions with a VCL scope. The REGEX type is only meant for regular expression literals managed by the VCL compiler. For dynamic regular expressions or complex usage see the API from the ``include/vre.h`` file. STRING C-type: ``const char *`` A NUL-terminated text-string. Can be NULL to indicate a nonexistent string, for instance in:: mymod.foo(req.http.foobar); If there were no "foobar" HTTP header, the vmod_foo() function would be passed a NULL pointer as argument. STEVEDORE C-type: ``const struct stevedore *`` A storage backend. STRANDS C-Type: ``const struct strands *`` Strands are a list of strings that gets passed in a struct with the following members: * ``int n``: the number of strings * ``const char **p``: the array of strings with `n` elements A VMOD should never hold onto strands beyond a function or method execution. See ``include/vrt.h`` for the details. TIME C-type: ``double`` Unit: seconds since UNIX epoch. An absolute time, as in 1284401161. VCL_SUB C-type: ``const struct vcl_sub *`` Opaque handle on a VCL subroutine. References to subroutines can be passed into VMODs as arguments and called later through ``VRT_call()``. The scope strictly is the VCL: vmods must ensure that ``VCL_SUB`` references never be called from a different VCL. ``VRT_call()`` fails the VCL for recursive calls and when the ``VCL_SUB`` cannot be called from the current context (e.g. calling a subroutine accessing ``req`` from the backend side). For more than one invocation of ``VRT_call()``, VMODs *must* check if ``VRT_handled()`` returns non-zero in-between calls: The called SUB may have returned with an action (any ``return(x)`` other than plain ``return``) or may have failed the VCL, and in both cases the calling VMOD *must* return also, possibly after having conducted some cleanup. Note that undoing the handling through ``VRT_handling()`` is a bug. ``VRT_check_call()`` can be used to check if a ``VRT_call()`` would succeed in order to avoid the potential VCL failure. It returns ``NULL`` if ``VRT_call()`` would make the call or an error string why not. VOID C-type: ``void`` Can only be used for return-value, which makes the function a VCL procedure. .. _ref-vmod-symbols: C symbols ========= Through generation of ``vcc_if.h``, ``vmodtool.py`` pre-defines the names of most symbols on the C side of the vmod interface, namely: * function names as *_* * event handler names as *_* * method names as *__*, with two special methods named * ``_init`` for the constructor and * ``_fini`` for the destructor * class struct names as *__* * argument struct names for support of optional arguments as *arg___* for functions and *arg____* for methods, with member names * *valid_* for the flag of optional arguments being present and * ** for the argument name * enum values as *enum___* For the above, the ** placeholders are defined as: ** The ``$Prefix`` stanza value, if defined in the ``.vcc`` file, or ``vmod`` by default. ** The vmod name fro the ``$Module`` stanza of the ``.vcc`` file. ** The function or method argument *cname* or, if not given, *vclname* as specified using the *:* syntax. The other placeholders should be self-explanatory as the name of the respective function, class, method or handler. In summary, symbol names can either be influenced by the vmod author globally using ``$Prefix``, or using the *:* syntax for argument names. .. _ref-vmod-private-pointers: Private Pointers ================ It is often useful for library functions to maintain local state, this can be anything from a precompiled regexp to open file descriptors and vast data structures. The VCL compiler supports the following private pointers: * ``PRIV_CALL`` "per call" private pointers are useful to cache/store state relative to the specific call or its arguments, for instance a compiled regular expression specific to a regsub() statement or simply caching the most recent output of some expensive operation. These private pointers live for the duration of the loaded VCL. * ``PRIV_TASK`` "per task" private pointers are useful for state that applies to calls for either a specific request or a backend request. For instance this can be the result of a parsed cookie specific to a client. Note that ``PRIV_TASK`` contexts are separate for the client side and the backend side, so use in ``vcl_backend_*`` will yield a different private pointer from the one used on the client side. These private pointers live only for the duration of their task. * ``PRIV_TOP`` "per top-request" private pointers live for the duration of one request and all its ESI-includes. They are only defined for the client side. When used from backend VCL subs, a NULL pointer will potentially be passed and a VCL failure triggered. These private pointers live only for the duration of their top level request .. PRIV_TOP see #3498 * ``PRIV_VCL`` "per vcl" private pointers are useful for such global state that applies to all calls in this VCL, for instance flags that determine if regular expressions are case-sensitive in this vmod or similar. The ``PRIV_VCL`` object is the same object that is passed to the VMOD's event function. This private pointer lives for the duration of the loaded VCL. The ``PRIV_CALL`` vmod_privs are finalized before ``PRIV_VCL``. The way it works in the vmod code, is that a ``struct vmod_priv *`` is passed to the functions where one of the ``PRIV_*`` argument types is specified. This structure contains three members:: struct vmod_priv { void *priv; long len; const struct vmod_priv_methods *methods; }; The ``.priv`` and ``.len`` elements can be used for whatever the vmod code wants to use them for. ``.methods`` can be an optional pointer to a struct of callbacks:: typedef void vmod_priv_fini_f(VRT_CTX, void *); struct vmod_priv_methods { unsigned magic; const char *type; vmod_priv_fini_f *fini; }; ``.magic`` has to be initialized to ``VMOD_PRIV_METHODS_MAGIC``. ``.type`` should be a descriptive name to help debugging. ``.fini`` will be called for a non-NULL ``.priv`` of the ``struct vmod_priv`` when the scope ends with that ``.priv`` pointer as its second argument besides a ``VRT_CTX``. The common case where a private data structure is allocated with malloc(3) would look like this:: static void myfree(VRT_CTX, void *p) { CHECK_OBJ_NOTNULL(ctx, VRT_CTX_MAGIC); free (p); } static const struct vmod_priv_methods mymethods[1] = {{ .magic = VMOD_PRIV_METHODS_MAGIC, .type = "mystate", .fini = myfree }}; // .... if (priv->priv == NULL) { priv->priv = calloc(1, sizeof(struct myfoo)); AN(priv->priv); priv->methods = mymethods; mystate = priv->priv; mystate->foo = 21; ... } else { mystate = priv->priv; } if (foo > 25) { ... } Private Pointers Memory Management ---------------------------------- The generic malloc(3) / free(3) approach documented above works for all private pointers. It is the simplest and less error prone (as long as allocated memory is properly freed though the fini callback), but comes at the cost of calling into the heap memory allocator. Per-vmod constant data structures can be assigned to any private pointer type, but, obviously, free(3) must not be used on them. Dynamic data stored in ``PRIV_TASK`` and ``PRIV_TOP`` pointers can also come from the workspace: * For ``PRIV_TASK``, any allocation from ``ctx->ws`` works, like so:: if (priv->priv == NULL) { priv->priv = WS_Alloc(ctx->ws, sizeof(struct myfoo)); if (priv->priv == NULL) { VRT_fail(ctx, "WS_Alloc failed"); return (...); } priv->methods = mymethods; mystate = priv->priv; mystate->foo = 21; ... * For ``PRIV_TOP``, first of all keep in mind that it must only be used from the client context, so vmod code should error out for ``ctx->req == NULL``. For dynamic data, the *top request's* workspace must be used, which complicates things a bit:: if (priv->priv == NULL) { struct ws *ws; CHECK_OBJ_NOTNULL(ctx->req, REQ_MAGIC); CHECK_OBJ_NOTNULL(ctx->req->top, REQTOP_MAGIC); CHECK_OBJ_NOTNULL(ctx->req->top->topreq, REQ_MAGIC); ws = ctx->req->top->topreq->ws; priv->priv = WS_Alloc(ws, sizeof(struct myfoo)); // ... same as above for PRIV_TASK Notice that allocations on the workspace do not need to be freed, their lifetime is the respective task. Private Pointers and Objects ---------------------------- ``PRIV_TASK`` and ``PRIV_TOP`` arguments to methods are not per object instance, but per vmod as for ordinary vmod functions. Thus, vmods requiring per-task / per top-request state for object instances need to implement other means to associate storage with object instances. This is what ``VRT_priv_task()`` / ``VRT_priv_task_get()`` and ``VRT_priv_top()`` / ``VRT_priv_top_get()`` are for: The non-get functions either return an existing ``PRIV_TASK`` / ``PRIV_TOP`` for a given ``void *`` argument or create one. They return ``NULL`` in case of an allocation failure. The ``_get()`` functions do not create a ``PRIV_*``, but return either an existing one or ``NULL``. By convention, private pointers for object instance are created on the address of the object, as in this example for a ``PRIV_TASK``:: VCL_VOID myvmod_obj_method(VRT_CTX, struct myvmod_obj *o) { struct vmod_priv *p; p = VRT_priv_task(ctx, o); // ... see above The ``PRIV_TOP`` case looks identical except for calling ``VRT_priv_top(ctx, o)`` in place of ``VRT_priv_task(ctx, o)``, but be reminded that the ``VRT_priv_top*()`` functions must only be called from client context (if ``ctx->req != NULL``). .. _ref-vmod-event-functions: Event functions =============== VMODs can have an "event" function which is called when a VCL which imports the VMOD is loaded or discarded. This corresponds to the ``VCL_EVENT_LOAD`` and ``VCL_EVENT_DISCARD`` events, respectively. In addition, this function will be called when the VCL temperature is changed to cold or warm, corresponding to the ``VCL_EVENT_COLD`` and ``VCL_EVENT_WARM`` events. The first argument to the event function is a VRT context. The second argument is the vmod_priv specific to this particular VCL, and if necessary, a VCL specific VMOD "fini" function can be attached to its "free" hook. The third argument is the event. If the VMOD has private global state, which includes any sockets or files opened, any memory allocated to global or private variables in the C-code etc, it is the VMODs own responsibility to track how many VCLs were loaded or discarded and free this global state when the count reaches zero. VMOD writers are *strongly* encouraged to release all per-VCL resources for a given VCL when it emits a ``VCL_EVENT_COLD`` event. You will get a chance to reacquire the resources before the VCL becomes active again and be notified first with a ``VCL_EVENT_WARM`` event. Unless a user decides that a given VCL should always be warm, an inactive VMOD will eventually become cold and should manage resources accordingly. An event function must return zero upon success. It is only possible to fail an initialization with the ``VCL_EVENT_LOAD`` or ``VCL_EVENT_WARM`` events. Should such a failure happen, a ``VCL_EVENT_DISCARD`` or ``VCL_EVENT_COLD`` event will be sent to the VMODs that succeeded to put them back in a cold state. The VMOD that failed will not receive this event, and therefore must not be left half-initialized should a failure occur. If your VMOD is running an asynchronous background job you can hold a reference to the VCL to prevent it from going cold too soon and get the same guarantees as backends with ongoing requests for instance. For that, you must acquire the reference by calling ``VRT_VCL_Prevent_Discard`` when you receive a ``VCL_EVENT_WARM`` and later calling ``VRT_VCL_Allow_Discard`` once the background job is over. Receiving a ``VCL_EVENT_COLD`` is your cue to terminate any background job bound to a VCL. You can find an example of VCL references in vmod-debug:: priv_vcl->vclref = VRT_VCL_Prevent_Discard(ctx, "vmod-debug"); ... VRT_VCL_Allow_Discard(&ctx, &priv_vcl->vclref); In this simplified version, you can see that you need at least a VCL-bound data structure like a ``PRIV_VCL`` or a VMOD object to keep track of the reference and later release it. You also have to provide a description, it will be printed to the user if they try to warm up a cooling VCL:: $ varnishadm vcl.list available auto/cooling 0 vcl1 active auto/warm 0 vcl2 $ varnishadm vcl.state vcl1 warm Command failed with error code 300 Failed Message: VCL vcl1 is waiting for: - vmod-debug In the case where properly releasing resources may take some time, you can opt for an asynchronous worker, either by spawning a thread and tracking it, or by using Varnish's worker pools. When to lock, and when not to lock ================================== Varnish is heavily multithreaded, so by default VMODs must implement their own locking to protect shared resources. When a VCL is loaded or unloaded, the event and priv->free are run sequentially all in a single thread, and there is guaranteed to be no other activity related to this particular VCL, nor are there init/fini activity in any other VCL or VMOD at this time. That means that the VMOD init, and any object init/fini functions are already serialized in sensible order, and won't need any locking, unless they access VMOD specific global state, shared with other VCLs. Traffic in other VCLs which also import this VMOD, will be happening while housekeeping is going on. Statistics Counters =================== Starting in Varnish 6.0, VMODs can define their own counters that appear in *varnishstat*. If you're using autotools, see the ``VARNISH_COUNTERS`` macro in varnish.m4 for documentation on getting your build set up. Counters are defined in a .vsc file. The ``VARNISH_COUNTERS`` macro calls *vsctool.py* to turn a *foo.vsc* file into *VSC_foo.c* and *VSC_foo.h* files, just like *vmodtool.py* turns *foo.vcc* into *vcc_foo_if.c* and *vcc_foo_if.h* files. Similarly to the VCC files, the generated VSC files give you a structure and functions that you can use in your VMOD's code to create and destroy the counters your defined. The *vsctool.py* tool also generates a *VSC_foo.rst* file that you can include in your documentation to describe the counters your VMOD has. The .vsc file looks like this: .. code-block:: none .. varnish_vsc_begin:: xkey :oneliner: xkey Counters :order: 70 Metrics from vmod_xkey .. varnish_vsc:: g_keys :type: gauge :oneliner: Number of surrogate keys Number of surrogate keys in use. Increases after a request that includes a new key in the xkey header. Decreases when a key is purged or when all cache objects associated with a key expire. .. varnish_vsc_end:: xkey Counters can have the following parameters: type The type of metric this is. Can be one of ``counter``, ``gauge``, or ``bitmap``. ctype The type that this counter will have in the C code. This can only be ``uint64_t`` and does not need to be specified. level The verbosity level of this counter. *varnishstat* will only show counters with a higher verbosity level than the one currently configured. Can be one of ``info``, ``diag``, or ``debug``. oneliner A short, one line description of the counter. group I don't know what this does. format Can be one of ``integer``, ``bytes``, ``bitmap``, or ``duration``. After these parameters, a counter can have a longer description, though this description has to be all on one line in the .vsc file. You should call ``VSC_*_New()`` when your VMOD is loaded and ``VSC_*_Destroy()`` when it is unloaded. See the generated ``VSC_*.h`` file for the full details about the structure that contains your counters. .. _ref-vmod-tmpdir: Temporary Files =============== ``varnishd`` creates a directory named ``worker_tmpdir`` under the varnish working directory (see ``varnishd -n`` argument) for read/write access by the worker process. From the perspective of VMODs, the relative path is always ``worker_tmpdir``. This directory is intended (though not limited) to provide a place for VMODs to create temporary files using ``mkstemp()`` and related libc functions. VMODs are responsible for cleaning up files which are no longer required, and they will ultimately be removed when the ``varnishd`` worker process restarts. There is no isolation between VMODs (as is the case anyway). A simple example for how to use it:: #include #include #include "vdef.h" #include "vas.h" static void tmpfile_example(void) { int fd; char name[] = "worker_tmpdir/myvmod.XXXXXX"; fd = mkstemp(name); if (fd < 0) { // handle error return; } // hide file AZ(unlink(name)); // use fd AZ(close(fd)); } Henceforth, whatever our philosopher says about Matter will apply to extension and to extension alone. It cannot be apprehended by sight, nor by hearing, nor by smell, nor by taste, for it is neither colour, nor sound, nor odour, nor juice. Neither can it be touched, for it is not a body, but it becomes corporeal on being blended with sensible qualities. And, in a later essay, he describes it as receiving all things and letting them depart again without retaining the slightest trace of their presence.483 Why then, it may be asked, if Plotinus meant extension, could he not say so at once, and save us all this trouble in hunting out his meaning? There were very good reasons why he should not. In the first place, he wished to express himself, so far as possible, in Aristotelian phraseology, and this was incompatible with the reduction of Matter to extension. In the next place, the idea of an infinite void had been already appropriated by the Epicureans, to whose system he was bitterly opposed. And, finally, the extension of ordinary327 experience had not the absolute generality which was needed in order to bring Matter into relation with that ultimate abstraction whence, like everything else, it has now to be derived. That the millionaire was genuine, ¡°in person and not a caricature,¡± as Dick put it, was evident. Both the nurse, his relative, and his wife, were chatting with him as Jeff delivered the heavy packed ball made up of the gum. 233 "I guess not," said Landor, tolerantly, as he turned[Pg 106] his horse over to his orderly; "but, anyway," he added to Ellton, "we had a picnic¡ªof a sort." Si, unable to think of anything better, went with him. The train had stopped on a switch, and seemed likely to rust fast to the rails, from the way other trains were going by in both directions. The bridge gang, under charge of a burly, red-faced young Englishman, was in the rear car, with their tools, equipments, bedding and cooking utensils. THE DEACON HAS SOME EXPERIENCES WITH THE QUADRUPED. "You are not within a mile of the truth. I know it. Look here: I believe that is Gen. Rosecrans's own cow. She's gone, and I got an order to look around for her. I've never seen her, but from the description given me I believe that's she. Who brought her here?" "Deacon, these brothers and sisters who have come here with me to-night are, like myself, deeply interested in the moral condition of the army, where we all have sons or kinsmen. Now, can't you sit right there and tell us of your observations and experiences, as a Christian man and father, from day to day, of every day that you were down there? Tell us everything, just as it happened each day, that we may be able to judge for ourselves." HAS AN ENCOUNTER WITH THE PROVOST-MARSHAL. "Wonder which one o' them is the 200th Injianny's?" said Si to Shorty. "And your mother, and Harry?" The daughter must be the girl who was talking to him now. She sat on a little stool by the fire, and had brought out some sewing. "Over at Grandturzel¡ªcan't see wot's burning from here. Git buckets and come!" These things, however, gave little concern to the worthy who commanded the Kentish division. Tyler, though an excellent blacksmith, possessed few of the qualities requisite for forming a good general. Provided there was no very sensible diminution in the number of his followers, he cared not a straw for the score or two who, after quarrelling, or perhaps fighting, withdrew in such disgust that they vowed rather to pay the full tax for ever than submit to the insolence of the rebels. One man could fight as well as another, reasoned he; and, provided he was obeyed, what mattered it by whom. Dick went and Tom came¡ªit was sure to be all one in the end. But this burst of indignation soon passed away, and upon the suggestion of the prudent Sir Robert Hailes, he sent an evasive answer, with a command that the Commons should attend him at Windsor on the Sunday following. That it was a stratagem to gain entrance to the Tower, was the opinion of several, but, after much discussion, it was decided that the man should be admitted, and that the monk should be exhibited merely to intimidate the rebels, until the result of this promised communication should be known. HoMEŮͬÐÔÁµcbcb ENTER NUMBET 0017
quanliba.com.cn
muwu0.com.cn
gaosi4.net.cn
sixie2.com.cn
lima9.net.cn
xuer7.net.cn
manna8.net.cn
www.nayao6.com.cn
www.ahwoman.org.cn
ermin1.com.cn
张柏芝露b 尻逼逼影院 人体艺术avav 动漫黑人图 五月天欧美色图片 小妹妹人艺体艺术 三集片huaog WWW.JIJIZY.COM WWW.USQ6.COM WWW.85KKKK.COM WWW.QI-WEN.COM WWW.SE9992.COM WWW.09ZZZZ.COM WWW.HNLYTF.COM WWW.TJKPZX.COM WWW.ZXSP68.COM WWW.HHH840.COM WWW.MV94.COM WWW.114066.COM WWW.61PPS.COM WWW.313K.COM WWW.HHH131.COM WWW.CL611.COM WWW.WJJSOFT.COM WWW.976QQ.NET WWW.RE219.COM WWW.TTXUTZF.COM WWW.410R.COM ABU.OMAR WWW.74TGG.COM WWW.18AVDAY.COM WWW.BBB710.COM WWW.CWGRC.COM WWW.AA717.COM WWW.H9XR.COM gehentaiorg 哥哥姐姐综合社区 av毛片无码片 99re5久久热在线播放快 俄欧美妈妈与儿子乱伦 骚逼被操视频哥哥去哥哥色爱操逼 好好干亚洲老太太b WWW44rerecon www9696h wwwasw4444com 依依社区人妻图片 东京热苍井空QVOD www_东京热_com 意淫强奸人妻女友 真人性爱姿势电影 淫系列 有声书收听 免费av在线看 在我AV天堂 www日本黄片 日韩千部黄色电影 2012天堂伦理最新加勒比 唐山大兄 在线哥哥去 一木道福利 草榴社区2016 插我的小tube avtt2020 亚洲性爱-脱光干X网 WWW_ANQUYE789_COM 久久热集百万潮流 www5060lucom av999偷拍自拍 濑亚美莉磁力连接 成人美女游戏 色色网激情视频学生 手机版人与动物啪啪 清纯女友被轮奸调教 午夜网址大全 刺激撸的网站 久久影音手机版下载百度云 游戏人体艺术 q播自拍偷拍 wwwxxooluolicom 监狱里的大鸡巴 羞涩影院会员 www903sscom 石家庄少女的性爱视频 日本儿子五月天 黄色片xxx 熟女成人乱伦做爱免费视频 骚鸡鸡 2015狼人av综合 www7xpxpcomftp 全国黄色片子 美国新农夫综合 wwwmcc222com 岳母在线观看 日日射日一日fi79com 萝莉h在线看视频 港台美女 变态另类欧美性爱av天堂2014 wwwnn535c慰m Www331com 古墓丽影h版免费观看 国产父女乱伦小说 蔡依林纹身图案 女人17P 强奸乱伦最稳定网站 自偷自拍百度百度 日本激情点的床上男女 坠落色戒 凌辱女友mcc色站 亚洲男女淫秽乱伦性交色图 wwaisedizhicomcom 作者不详bt工厂 91porm手机端 新新影院若怒 人妖性爱高潮图片 CK在线看 日本阴户视频美国人曾交 熟女露逼口交 国产图片成人av小说wwwlsy2016com sm车神 www115cdcom 大奶娴的调教qk3pcom 爷爷和孙女乱伦影片 美女做爱自拍25P 亚洲欧美色片在线播放 日本丝袜熟妇乱伦 琪琪自拍偷拍 黑丝诱惑亚州性夜夜射 412vvcom www510ddc5cbiz 骚逼姐姐的大屁股 色色鸡巴图片 cluanlun 大肥婆性爱 尤娜种子 00后人体图片少女无毛掰开图片 快播人与马交配 全祼体女张筱雨 乐乐形式亚洲色图 偷拍自拍模特mb 成人在线骚逼女人 高清图片网站裸体丝袜熟妇 色 五月天 婷婷 快播 抽插逼图片 11xingjiao 拳交 am 人体艺术女人最大胆的高清阴道全裸图 好色猫欧亚色图 人与曽肏屄播放 baguacaobi 同志做爱视屏 2014吉吉影音三级片 成人美女贴图 人體圖片網 色色人导航 天天撸夜夜撸高清色图大图 插美人老师 WWW_JDMI_COM hp之报应来得快 天籁地球村 名字测 董文华儿子 鞋子大全 亚洲视频新 日本人体里美尤利娅 草比阴影先锋 张柏芝的黑木耳西瓜 美女老师光屁股 猛插青空小夏骚穴图 日本人口交图 熟女肛交30p wwwdd43com 少妇大胆阴部大bb图片 快播ay 张柏芝艳照门高清下载 sao8080c 美女美穴图片30p 乱伦大鸡吧操逼故事 五月天duppid1 mac版淫色网站 岸明日香ed2k 色撸撸色图 惊变激情戏在多少分钟 人体艺术大图下载 圣后骚货 高清无码母乱伦 8090色色网 美女图片大胸删除 明星性交合成骚图 大胆漏阴人体艺术 美女行爱视频 插娇艳欲滴片阴 光棍影院丫丫11111 超碰最新视频精品视频wwwjd993com 淫淫操淫淫逼 女人露全乳图片 久草在线资草免 暴露女友轮奸 美女骚穴值得一日15P 欧美阿v女星播放 曰本色惰 国产超级法在线 色狗成年综合伊人 俄罗斯成人免费视频gegequlucom 33连导航农夫十次了 日本丰满肉弹熟妇 大香蕉伊人Tv 搜索色色色生香 三浦敦子mp4 伊人香蕉网WWWtr668com 黄色视频播放器wwwyehaobo7com 学姐的卫生巾 wwwse青青草com 骚美女36D 村上理沙手机在线播放 胔死我了爽啊 麻椒直播百度百科 岛国肉戏片在线下载 色中色成人黄色影院 12p黄色 爸别舔了啊轻点 超碰视频在线am 外国人做爱爽图片 有没有不不需要播放器的毛片 shkd官网 狼人干综合在线视频久久14iycom 黄色录像同性恋口交 处女红舒淇 熟女您射 有声小说推荐 诗春色 小泽玛利亚成长 小泽玛利亚现在 没病毒的h网 www酷狗音乐com www小沈阳com 四方伯伯开心五月天 精彩电影 天然素人 我也去色 妹妹AV综合 强奸迷奸做爱 910668快播 色大姐 撸撸管 doa成人电影 天堂网014 男同chinese帅哥gav玄兵 牛叉b电影435yy 千人斩的电影天堂 乱伦视频app 亚洲AV外卖 migd-4188 白鸟寿美礼电影伦理片 水之声动漫 wwwes18 妹子被干B 性感女秘书肉丝超短裙加班时被经理扑倒操爽后说 我等下要喷潮了 好痒啊 你快点 办 心动网址你懂视频 曰韩后入视频 日本情爱电影 日韩AB首汉-尿色电影 人人干人人 ts 艾彩trample 轻轻搞m3u8 新视觉a 五月丁香综合缴情香蕉 2014Aⅴ天堂 色奶妈在线 4hu 1122 在线偷拍自拍图片 97视频日本一本道 强奸超碰视频 黄图女性全身照 haodiaoyin这里只有精 凹凸视频 youjiz 吾爱久草福利导航 超碰视频在线美女逼 bunnybunnylove福利 伦理片adfy 流氓医生和俏护士视频 欧美强奸视频在线网站 777福利导航 直播偷拍在线观看视频 i8宝马影院在线 做爱黄福利影院 嘬大鸡巴 五月青青草 国产夫妻找人玩3p漂亮媳妇被单男猛操连续高潮磁力 外国XⅩx在线 高清无码色欲迷墙 jufd_409在线观看 hu99 播菊网 人人看人人爱人人妻 欧美性爱网进口 成人caohub AVOP127无码 ftp 冯熙璇 (春夏女装) -(帆布鞋) 东北娇妻土豪视频 X 影片名:网红美女演绎学生看到老师穿着高跟丝袜很性感就尾随跟到家里和老 国产成人啪啪自拍 91免费免费视频在线观看噜噜 SD001丝袜电影 欧美图片自拍图片 111pdy最新地址 久久热在线视频国产91大神熊哥 色酷狠狠干 wwwAV手机 手机看片动图 色偷拍亚洲偷自拍在线视频 筋流在线播放 757午夜福利影视1000 米奇大香蕉在线视频 百度热搜推荐乱伦自拍 西瓜影音 k8经典邱淑贞 无影院码 将军肉公主成人漫画 av在线日本人妻无码 亚洲欧美中文日韩在线无码 av淘宝视频在线分类 拉风色国产 初中白丝自慰 SHIB-026 神山美羽 魅惑の縦スジ 绿茶导航国产 午夜福利236 超薄丝袜约炮 制服诱惑快播涩 日本高清无码美女视频 日本性乱交视频 丝袜在线观看综合 97起碰在线自拍 3344动画伦理片 在线拍 A级片互舔 2828sezy 学院女神 富二代三亚 萝莉学生视频 大象视频福利 香艳视频集锦 学生妹诱惑福利合集 magnet 邪恶里番肉番 香蕉视视频app 消失的说说日本伦理 日本一本道黄色视频在线播放 美国成人综艺节目磁力链接 里番无修手机在线看 松岛绫花步兵下载 亚洲 日韩 在线 制服 午夜高清自拍 狂胔美女空姐小说 大学生偷拍自拍 免费操逼黄片大全 rion 先锋在线 俄罗斯性爱茄视频 久播 福利 内射av小视频 主播 和 狗 交 配视频在线观看 福利小电影在线观看免费观看 干阴逼 MIAD-937 magnet 一本道,东京热第一页 abp561c 毛片激情直播网站 86手机在线看a片资源 国产偷拍 欧洲激情 操碰色区 999xdv 777影院 亚洲性直播live 红阁番影院 日本一本高清无码mv 22bbbb 亚洲人成网站在线播放图片 第一综合色站 real睿宝内部V8视频种子 国产真实偷拍啪视 在大街上穿着裙子没带自慰棒视频。 logdown永久地址 手机看黄片红楼梦 日本天天干 午夜11p 日本鲜肉gv百度云 啄木鸟在线观看免费 4tubesex deos曰本 a性交视频 成人手机福利,车上各种 俄罗斯美女裸体黄片 日本高清视频网页 爵迹2迅雷磁力链接 不用下载的免费操逼视频 综合色爱视频 黄色美女干黄色事 换妻性交真实影片 久久国产在线野战 AV淘宝2018在线 4438成人网(开心五月) 国产综合色 xo168惰色在线 南里美希泳装 手机自拍偷拍强奸乱伦 超碰成年人福利无码 日本女人女同视频 麻生千春视频 极品外围女模特拍摄时被摄影师勾引 拳脚周晓林在线播放 先锋影音:超模全裸大片 安全的免费av 沉香 性欲 邱县特级黄片 立川理惠七夕电影在线 美女被孼 国产自拍伦理电影 日韩理论大全视频 淫妻小说 爱丝小仙女思妍白丝 熊猫tv杜姗姗私人视频 和刚下班的白领在洗手间 好看的中文字幕色拍拍噜 92福利自拍 AEEN资源 迅雷 下载欧美女优 国外一级录像 熟女性生活视频在线观看 莲实克蕾儿 中文在线 91秦先生小明看看 冴岛香织在线av AV在线论坛 江疏影2分钟视频链接 那种女的虐女的番号 亚州福利电影 国产张飞跃在线播放 国产自拍第9页 韩国三级理论福利视频 色吧 春暖花开春暖花开 最新福利短视频在线 手机在线好吊草视频 国产超高级自拍 龙腾色狼 性交2018国产久久精采视频 网红h视频迅雷下载 magnet 国产a片作品 2017亚洲天堂在线av电影网 苍空 手机观看网哈 xⅩxSex 4438x 1成人网 奸轰片 国产自拍欧美视频 huangsedepian 亚洲成八综合视频 第四色先锋色色 国产熟妻女人在线视频 人妻生活前编在线观看 欧美爱爱插小 黄s网大全 少女水逼 色人党苍井空 俺也撸激情明星 在露沐浴和大奶子美女做爱 做爱黄色图片网站 优酷爱疯主播分成 和丝袜老师做爱 999色网 苍井空的色墙 被男友狠狠玩奶子骚穴 日本国模人体艺术图片 裸体性感欧洲帅哥 白虎裸体艺术 最新豚眠影音先锋 恋足舔脚视频 色99色 132renti 大学生援交50p 欧美色图很很lou 我把岳母操的狂叫 大胆人体组图 马六人体高贵美 妇 女人秘密处动态照 性感黑丝小骚逼 WWW_BBSTT86_COM 天堂岛男人的天堂 少妇爱大鸟【15p】怡春院百度 大战熟女记txt 日本漫画的人体艺术 哥哥射 p 操乡下熟鸡 夜射猫在线播放 岳母和女讯做爱 国产cenren 美女嫩逼50 谷歌大胆人体艺术图片 ed2k无码女同番号 空姐的秘密狠狠干 梦意杀机 北京函授大学 亚洲成人美女性交区 泰妹性交做爱 狠狠影院下载 WWW_WW945VV_COM 张筱雨棵体艺术写真集 不穿衣服的美浪妇 草别人媳妇 成人花花公子导航 日本美女裸体大全 xunleimianfeidianyingxiazai 妈妈操逼色色色视频 狠狠干meinurenti aiyishu 插老师导航 avhbocom 那英性爱1级片 欧美操屄上视频 我想和亲妈发生过关系 黑人干美女的的电影 国内丝袜大妈图片 美女大胆人体丝袜 400色色色 chabibiantai 国内乱妇乱伦 stoya图片裸照 黄色3及 色妹妹口交吃精 小明看看平台se7se7 熟女大姨 人与兽影音先锋播放 宫本由美淫 有人体色图 明星色图29 辽大bt 日韩孕妇做爱 乱伦文章天天色 我的妈妈是淫荡老师五十熟女 喷奶三级片 WWW777VFCOM 欧美与亚洲色片 换妻不要停快操我的屄 饭冈加奈子男人最喜欢的类型网传 最大胆亚洲裸体艺术 国产自拍土逼视屏 拍照做爱 我被两个老外抱着干 狂插白洁 强奸伦理片 逼图片第26p 亿性家社区视频 成人片最新狼友 733动漫网成人片影音先锋 姐妹妈妈阿姨日逼 综合插插a 日本A片899jjcom 岛国鲁炸天在线影院 欧美性交操b 2017丝袜少妇贴吧 好想要性生活 欧美成人教育片巨乳wwwmjlnihydbufcn savsopwcn 小说区视频区欧美时尚自拍偷拍 成人丽丽 亚洲性va在线观看百度 淫妻丝袜小说网 骚妻小莹 操性奴女 白虎人体艺术 亚州淫性片 中年操 佐山爱女友的姐姐下载 大香蕉之肥胖熟妇在线视频 古典武侠第四色色午夜 成濑心美2017人体 免下载偷拍黄色 风流少妇人体艺术图片 欧美桃在影院 性感丝袜漫画美女图片 免费看欧美黄色大片网站xxx 家庭老师姐姐的诱惑漫画 男孩操的女孩好爽视频播放 舔大学美脚微博 天津爆打桩系列在线 wwwcaoxiu184co 噜wwwav567net 日韩黄色女忧 欧美男女操逼图像 图片色姐妹 老岳母的肥乳 在线成人电影免播放器免下载2014成人视频免费在线观看 自拍丝袜欧美偷拍 美乳翘臀自拍偷拍 成人电影实战 少女手淫偷拍视频 奸入女儿 www图图成人站 表姐在车上让我插穴 超市强暴在线 亚洲巨乳少女色27p nass系列合集 偷拍自拍自拍一区在线观看 3p4p做爱 成人有声读物 上了个美女亚洲色图 metartvideosxxx av大腿夹射系列 能手机在线看的福利长片 爆乳美女无码15p 夜射猫精品乱伦 青楼社区免费观看 另类专区自慰在线wwwhhxxoo1com wwwzly99com 人人操色8 色网p 少妇激情综合站 熟女内裤艳照 成人偷拍自怕免费在线电影 逍遥牛牛官网 无毛小穴 7777avcom下载 妈妈撸狠狠干 wwwll777 大黑屄插插插 草榴社区2012网址 carporn欧美网站 顶破av片 黑老大插插 狠狠偷2016你懂得 aboutblank约炮 肉洞肉棍口交 撸管网址淫色帝国 中年同志叔叔的大老二 play视频资源 色尼姑色尼姑在线色尼姑图色尼姑影院 四房播狠狠撸 player亚洲有码 亚洲色图人妻乱伦手机版 jjaz_com黄色网 超碰羞羞 徐冬冬吃男人鸡巴视频 凌辱 武侠激情都市小说 大炮撸在线影院 清纯唯美激情五月姐姐 色阁第色季姐妹爱情 黄色片黄色视频黄色论理小说 长沙哪里有A片购买 美国妓院电影操我 色尼姑久久超碰视频在线 www五月天cm ttjh113dddcom 亚洲欧洲另类视频在线 极品日本熟女人妻 白领制服丝袜控在线视频 淫乱伦性爱电影 嫩女自拍 Xxoo88 114张悠雨魅惑图片色色看看色色看看主 老婆在我面前小说 真人性爱姿势动图 有什么外国人兽网站 wwwluluhetv女 和弟弟交尾 性交实拍舔鸡巴1000部 丝足交小说 美女明星的人体素像 www942tvcomwww942tvcom 看美女ys avdian126cmo 风暴AV天堂2015在线 褪色膏 大奶屄视频 ppypp影视天堂手机版 人人摸人人干888excom 成人动漫东方 性爱动漫在线免费 高清无码日本下载 小黄漫画书在线看 咪咪网络 苍井空人艺体图片大胆 裸体艺术爱人体ctrl十d ccc36色女孩 看兽性交 网友自拍暗暗撸 女人与兽做爱小说 人人色色成人专业操逼视频图 亚洲p炮综合图 熟了网 女优性交免费电影 鲁特特色中色影院先锋 caopiwangzhan 饭岛爱图片网 菠萝野结衣演过多少部电影 好看的电影特级黄色图片 兰桂坊人成在线视频 刑讯女小说 调教日本女优 wwwav777con 少年与熟妇爱图 女子与爱狗拔不出视频 哇嘎成个人社区米奇 熟女屄毛 风骚系2 小说 台湾强奸潮 操bi视频 美奶子 狠狠射狠狠操色妈妈色姐姐 激情乱伦口述 色狗中文字幕qvod 亚州偷拍自拍露奶子 女忧私处艺术 我在这里等你歌词 孤芳不自赏天天天影院 大学生做爱下载 丝袜内射吧 xxx大胆人体艺术 caoporen—在线视频 大胸长腿丝袜裸照美女 李宗瑞强奸mia 美女裸漏下阴 长泽锌胖瘦刚刚好的爆乳女吉吉 去撸吧社区亚洲视频 14岁儿子与母亲性交 大胆男人人体写真 WWWWWNNVCOM www844con 欧美色炮爱爱 做爱用品 妈妈再来一次波多野结衣快播 哪里有正规网站黄色小说 淫妻张敏阿红和公公乱伦 freefron快播 下一篇内射3p 真实的骚妇 欧美人妻肉射wwwqqqq68com 母婿口交乱伦 天天好逼百度影音 绝色贵妇丝袜小说 女厕所里熟女手淫视频 哥也色屄屄 舔阴蒂偷情 骚货操的你爽不爽 18岁以下禁止视频myoukucom 滛乱网www78iiiicom dizhi调教 日日夜夜鲁妈妈鲁播放人妖 狠狠射性感美女屁股图片 884aa在线wrsyioxjnlncn 琪怡红院 印度美女腋毛 中亚美女性爱图 电动抽插阳具下载 1314狠狠撸亚洲 jav女优网站 WWWKKKSSSC0m 欧美潮喷av网 wwwbbfulicomdianying AV群交游泳馆 咪咪爱网址最新百度 www优妓种子 黑屌曰幼女 黄色读书乱伦 明星av手机在线视频 春药催眠magnet 东京热淫乱人妻 裸体少妇阴道 另类有声小说 程蝶衣知春色 类似春色 樱井莉亚种子 小泽玛利亚av3gp 小泽玛利亚全片 求无毒h网 电脑能上的h网 色五月开心五月天 50268669东京热 手机可以看的黄片 黄网看黄片 黄色小说群 四房播 狼友之家 色既是空 高清做爱图 哥哥色在线 良人社导航 天天she app午夜快播免费1000 中国国产凤凰av 22 xhatmer 18 哥也色看不了 青青国产中文在线 轻吻也飘然 520少妇全集 全套服务在线云播 让人湿的文字 青草日日视频 讯雷哥云手机在线视频 人妻群p视频自拍 日韩 偷拍 自拍 在线 日本日日摸 女人天堂a视频区 茄子影院在线播放 手心影院黄色免费视频 乳交视频免费 f86080新视觉影院官网 259luxu日本线上资源 wwwsheshe88 欲色音影 日rrr 成人福利在线免费超级碰 4438xx1路com 番号去哪下载快 www,551777,com 人妻痴汉电车中文字幕 九九自拍视频在线观看 理论片老四影院 神马伦理不卡 国产自拍12 4蝥你V 治愈的不足的淫语引导到绝顶的回春旗袍 主播迷迭香磁力 早乙女由依视频手机在线观看 k45vcom平台樱桃 中文字幕成人 天天啪夜夜日日日干 电影港福利 大香蕉电影院 magnet 色狐狸av免费澳门 上原亚衣av片 wwwkk55kkcn 草民影音牛牛电影 欧美六九视频 AV黄色野战 我的世界女生自慰视频 大片播放器 x91毛片 出差招妓4P超爽 德国人xxx 成人影院看三级黄牛 大香蕉成绵乐 亚洲性爱米奇777 香港日本韩国台湾黄片 好看的国产自拍-最新国产自拍 17she009 亚洲激情无码视频 国产偷拍人妻自拍 汉庭酒店无码自拍 236宅宅网手 四虎影院紧急通道 ggmmkk 筋流在线播放 av电影大全亚洲天堂 大吊爆 葉S一红衣玩双奴视频 文静性感的大奶美女周日被男友带到出租屋挑逗后用尽全力操的美女说:我要,快点 vvvv999 伊人影院永久网址 色琪琪综合 XOXO未满十八岁勿进 色和日一本 白丝网站你懂的 成人视频在线天天喷 亚洲色逍遥社区com…… fset-487 绿衣超正初中妹三分钟 国产小黄片磁力链接 理伦片神马黑人 真人兔女郎福利视频 日本成人视频手机在线 MIAD-921中文 14girl色系 Japan inporn 酒店卫生间操女朋友 88titianm88 wwwnkmp66com 舔花核 小仙儿合集迅雷链接 性交视频新影院 学生自摸出水a片视频 处女操b电影 澳门香蕉操逼视频 东方库影,永久在线 若菜奈央716在线视频 911福利社区免费体验观看 福利 影院 bag 污直播视频还免费观看 日本三级做爱处女视频 强奸迅雷下载 magnet 2018午夜福利电影757影视 泰国美女需要体内射精在她的小阴户 桃色三国里番在线观看 俄罗斯另类三级小影院 熟女人妻 - 毛片基地 西瓜影音 轮奸路边小骚货干完还一人一泡尿迅雷 偷拍美女浴室伦理电影 夜店长裙番号种子 喵av 被窝久草影院 不卡的在线美女va视频 草榴影院中的黄色视频 被窝福利电影201 超碰超色超摸超操在线电影 太平天极jk 谁知道四虎影音最新地址 中文字幕rct-470在线 3d真人动漫xoxo漫画 十宗罪 ftp 喵喵AV网 彩色天堂网 操小逼出血视频 百人大战手机在线观看 成人逼b视频 vlc成人 操逼內射免费视屏 ssni209字幕网连接 siri自拍在线 有关很色的免费视频 在线视频播放你懂 华人play在线视频bbb kagp 019 丈夫不在家被肉棒操到红肿 喵了个咪av 蓝沢润 porn 珙琪影视在线观看 秋霞吧2017午夜电影 538在线精品牛牛 3手机激情在线成人影院 女主天地调教免费视频百度云 草莓在线视频免费观看e 不打码视频网 变形小雷 西瓜影音 国产偷拍第一页在线视频 下载黄片儿的。 mp4 视频里面看黄色与臀尖强奸情节故事视频里面看黄色录像强奸与通奸的故事 偷拍自拍第八十五 日本eeeex 一个美丽的嫩少妇15p 猫咪AV最新地址 成人影院官网 78福利影院伦理 无码xxxuom 俺来啦俺去啦新官网婷婷 国产自拍鸭子在线播放 怡红院依人香蕉 淫操初音女神 福利视频导航站 每日在线av免费视频每日更新 撸啵英视 裸体艺术广场舞资源在线播放 神马2018午夜影院 美国毛片基地A级e片 美国十次大公鸡 火山小黄福利视频 秋霞福利视频微拍 朴妮唛露私处完整视频 蚯蚓yy408 文在寅尻 99精品任你干 欧美日日B视频 抽插福利 偷拍广东情侣野战视频 jjzzseqing av福利资源 影豆网手机在线官网 二区每天更新不卡在线视频 花街在线AV 女人与狗ZOOXX 黄片男在上女在下视频免费 狠狠快点在线影视 小恶魔宇佐美奈奈 下载 亂倫文寃 白丝女主播自慰 德田重男作品迅雷种子全集资源 ibw619 影音先锋资源欧美啄木鸟剧情 律师娇妻之我妻只为他人淫 MSWD-10023 ftp 大屁股BT种子 色拍拍电影院 国内自拍在线偷拍大学色戒 嫩嫩影院 免费福利视频av 米歇尔贝瑞特 磁力下载 99y伦理 星野亚希校服 先锋 校园chunse tpzp 操心术在线观看 厚丝袜约炮 日本人口做爱姿势视频 美女午夜大片 15 H版暮光 开心激情网在线观看 乱伦儿媳妇大香蕉视频 迷干资源在线 gaonvnvnet 谁有艳照的网站 妈妈跟狗搞 欧美小姐120辣p图片 裸体后妈图 美女大尺度顶级图 小美女春暖花开亚洲 743vv 美女外拍全露出 亚洲蜜桃诱惑 爆插美女穴