All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Nikolay Borisov <kernel@kyup.com>
Cc: mszeredi@redhat.com,
	"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
	netdev@vger.kernel.org
Subject: Re: kernel BUG at net/unix/garbage.c:149!"
Date: Fri, 26 Aug 2016 22:24:26 +0200	[thread overview]
Message-ID: <1fbcb2c7-f004-4f2d-634e-a807dd5ec984@stressinduktion.org> (raw)
In-Reply-To: <CAJFSNy6rEpy7JcimW_jiOkgtWtDQgMaQJhcFHvRqgj92HibAvQ@mail.gmail.com>

On 25.08.2016 01:30, Nikolay Borisov wrote:
> On Thu, Aug 25, 2016 at 12:40 AM, Hannes Frederic Sowa
> <hannes@stressinduktion.org> wrote:
>> On 24.08.2016 16:24, Nikolay Borisov wrote:
> [SNIP]
>>
>> One commit which could have to do with that is
>>
>> commit fc64869c48494a401b1fb627c9ecc4e6c1d74b0d
>> Author: Andrey Ryabinin <aryabinin@virtuozzo.com>
>> Date:   Wed May 18 19:19:27 2016 +0300
>>
>>     net: sock: move ->sk_shutdown out of bitfields.
>>
>> but that is only a wild guess.
>>
>> Which unix_sock did you extract specifically in the url you provided? In
>> unix_notinflight we are specifically checking an unix domain socket that
>> is itself being transferred over another af_unix domain socket and not
>> the unix domain socket being released at this point.
> 
> So this is the state of the socket that is being passed to
> unix_notinflight. I have a complete crashdump so if you need more info
> to diagnose it I'm happy to provide it. I'm not too familiar with the
> code in question so I will need a bit of time to grasp what actually
> is happening.

Would probably be helpful. I couldn't spot anything so far
unfortunately. Also moving sockets over sockets which get closed
inflight seemed to work fine.

  reply	other threads:[~2016-08-26 20:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-24 14:24 kernel BUG at net/unix/garbage.c:149!" Nikolay Borisov
2016-08-24 21:40 ` Hannes Frederic Sowa
2016-08-24 23:30   ` Nikolay Borisov
2016-08-26 20:24     ` Hannes Frederic Sowa [this message]
2016-08-27  9:55   ` Miklos Szeredi
2016-08-29 22:37     ` Miklos Szeredi
2016-08-30  9:18       ` Miklos Szeredi
2016-08-30  9:31         ` Nikolay Borisov
2016-08-30  9:39           ` Miklos Szeredi
2016-09-01  9:13         ` Hannes Frederic Sowa
2016-09-27 14:16         ` Nikolay Borisov
2016-09-27 14:43           ` Hannes Frederic Sowa
2016-09-28  2:05           ` David Miller

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=1fbcb2c7-f004-4f2d-634e-a807dd5ec984@stressinduktion.org \
    --to=hannes@stressinduktion.org \
    --cc=kernel@kyup.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mszeredi@redhat.com \
    --cc=netdev@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.