public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Rainer Weikusat <rweikusat@mobileactivedefense.com>, davem@davemloft.net
Cc: edumazet@google.com, dhowells@redhat.com, ying.xue@windriver.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Joseph Salisbury <joseph.salisbury@canonical.com>
Subject: Re: https://patchwork.ozlabs.org/patch/579654?
Date: Tue, 16 Feb 2016 23:43:39 +0100	[thread overview]
Message-ID: <56C3A61B.2040004@stressinduktion.org> (raw)
In-Reply-To: <87bn7gv2mn.fsf@doppelsaurus.mobileactivedefense.com>

On 16.02.2016 21:09, Rainer Weikusat wrote:
> https://patchwork.ozlabs.org/patch/579654
>
> lists this as 'superseded', among with the older versions of the patch
> which changed the error handling. But at least, I couldn't find anything
> superseding it. This was supposed to address the different-but-related
> problem demonstrated by the following (slightly modified) test program:
>
> ---------
 > [...]
> --------
>
> Because the receiver has to wait for the message, it will hit the
> continue in unix_stream_read_generic. This causes the size-check of the
> do-while loop to be executed which terminates the loop as the size is
> zero without copying the credential information.
>
> Just wondering if this might have been lost in the noise ...

I think the patch got lost, probably just resending is the easiest 
solution. ;)

For the patch:
Acked-by: Hannes Frederic Sowa <hannes@stressinduktion.org>

Thanks,
Hannes

      reply	other threads:[~2016-02-16 22:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-16 20:09 https://patchwork.ozlabs.org/patch/579654? Rainer Weikusat
2016-02-16 22:43 ` Hannes Frederic Sowa [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56C3A61B.2040004@stressinduktion.org \
    --to=hannes@stressinduktion.org \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=edumazet@google.com \
    --cc=joseph.salisbury@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rweikusat@mobileactivedefense.com \
    --cc=ying.xue@windriver.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox