On 11/10/22 00:26, Eric Blake wrote:
> Modern qemu tends to advertise a strict 32M payload limit. Yet we
> default to allowing the user to attempt up to 64M in pwrite. For
> pread, qemu will reply with EINVAL but keep the connection up; but for
> pwrite, an overlarge buffer is fatal. It's time
On Thu, Nov 10, 2022 at 05:17:35PM +0100, Michal Orzel wrote:
> The code checking for CURLOPT_TLS13_CIPHERS option did not work
> properly, because of incorrect assumption that this symbol was a
> preprocessor macro. It is in fact element of enum type, which
> resulted with #ifdef directive
The code checking for CURLOPT_TLS13_CIPHERS option did not work
properly, because of incorrect assumption that this symbol was a
preprocessor macro. It is in fact element of enum type, which
resulted with #ifdef directive working improperly. Fix changes that
check to be based on curl version
And what about checking curl version (LIBCURL_VERSION_MAJOR,
LIBCURL_VERSION_MINOR) instead? That option was introduced in version 7.61, and
I see that You're using 7.21.
Please verify the second version if it would do its job.
Best regards,
Michał Orzeł
-Original Message-
From:
On 11/09/22 21:43, Eric Blake wrote:
> Make it possible for the sh and eval plugins to disconnect a client or
> shut down the entire nbdkit server by use of special return values.
> Prior to this patch we had reserved 4-7 for future use; this defines
> 4-8, and extends the set of reserved return
On Wed, Nov 09, 2022 at 01:47:15PM -0600, Eric Blake wrote:
> On Wed, Nov 02, 2022 at 01:36:26PM +, Richard W.M. Jones wrote:
> > > > -=item 4, 5, 6, 7
> > > > +=item S<4>
> > >
> > > The S<> notation seems new here (so it's going to be inconsistent with
> > > the rest of this file, I think).
On Thu, Nov 10, 2022 at 02:23:39PM +0100, Laszlo Ersek wrote:
> On 11/09/22 20:47, Eric Blake wrote:
> > On Wed, Nov 02, 2022 at 01:36:26PM +, Richard W.M. Jones wrote:
> -=item 4, 5, 6, 7
> +=item S<4>
> >>>
> >>> The S<> notation seems new here (so it's going to be inconsistent
On 11/09/22 21:43, Eric Blake wrote:
> We are about to define specific meaning to more return status values.
> To make it easier to probe if nbdkit is new enough to honor such
> definitions (and thus whether it makes sense to write a script that
> tries to utilize such special return values), it
On 11/09/22 20:47, Eric Blake wrote:
> On Wed, Nov 02, 2022 at 01:36:26PM +, Richard W.M. Jones wrote:
-=item 4, 5, 6, 7
+=item S<4>
>>>
>>> The S<> notation seems new here (so it's going to be inconsistent with
>>> the rest of this file, I think).
>>
>> I was going to mention this
