From: Guenter Roeck <linux@roeck-us.net>
To: Jun Wang <junwang123@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Herbert Xu <herbert@gondor.apana.org.au>,
Cong Wang <xiyou.wangcong@gmail.com>
Subject: Re: Glibc recvmsg from kernel netlink socket hangs forever
Date: Fri, 11 Mar 2016 15:50:35 -0800 [thread overview]
Message-ID: <20160311235035.GA18302@roeck-us.net> (raw)
In-Reply-To: <CANHDG4bEPkhWG1uhfswoCx=4M1u+QxEJ8TXQNfA=0kkBFjVSEw@mail.gmail.com>
On Fri, Mar 11, 2016 at 11:33:17AM -0800, Jun Wang wrote:
> > On 09/25/2015 08:55 AM, Herbert Xu wrote:
> >> On Thu, Sep 24, 2015 at 10:34:10PM -0700, Guenter Roeck wrote:
> >>>
> >>> Any idea what may be needed for 4.1 ?
> >>> I am currently trying https://patchwork.ozlabs.org/patch/473041/,
> >>
> >> This patch should not make any difference on 4.1 and later because
> >> 4.1 is where I rewrote rhashtable resizing and it should work (or
> >> if it is broken then the latest kernel should be broken too).
> >>
> > Yes, applying (only) the above patch to 4.1 didn't help.
> >
> >>> but I have no idea if that will help with the problem we are seeing there.
> >>
> >> Having looked at your message agin I don't think the issue I
> >> alluded to is relevant since the symptom there ought to be a
> >> straight kernel lock-up as opposed to just a user-space one because
> >> you will end up with the kernel sending a message to itself.
> >>
> >> And the fact that 4.2 works is more indicative as the bug is
> >> present in both 4.1 and 4.2.
> >>
> >> I'll try to reproduce this in 4.1 as time permits but no promises.
> >>
> >
> > I applied your patches (and a few additional netlink changes from 4.2)
> > to our 4.1 branch. I'll let you know if it makes a difference for us.
> >
> > Thanks,
> > Guenter
>
> Guenter,
>
> Which additional netlink changes from 4.2 did you patch? We still see
> the problem with your test program with 4.1.12 which have the
> following two patches mentioned by Herbert Xu on this thread.
>
Jun,
Sorry, I don't recall, and I no longer have access to the kernel since
I now work for a different company. I do recall that we had to apply
additional patches later, but I don't remember details.
Guenter
next prev parent reply other threads:[~2016-03-11 23:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 19:33 Glibc recvmsg from kernel netlink socket hangs forever Jun Wang
2016-03-11 23:50 ` Guenter Roeck [this message]
2016-03-12 0:13 ` Cong Wang
2016-03-12 1:25 ` Guenter Roeck
-- strict thread matches above, loose matches on Subject: below --
2015-09-25 0:29 Steven Schlansker
2015-09-25 4:36 ` Guenter Roeck
2015-09-25 4:58 ` Herbert Xu
2015-09-25 5:34 ` Guenter Roeck
2015-09-25 15:55 ` Herbert Xu
2015-09-25 16:14 ` Guenter Roeck
2015-09-26 3:45 ` Guenter Roeck
2015-09-25 21:37 ` Steven Schlansker
2015-09-25 21:54 ` Steven Schlansker
2015-09-26 2:58 ` Guenter Roeck
2015-10-05 23:26 ` Steven Schlansker
2015-10-05 23:30 ` Guenter Roeck
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=20160311235035.GA18302@roeck-us.net \
--to=linux@roeck-us.net \
--cc=herbert@gondor.apana.org.au \
--cc=junwang123@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xiyou.wangcong@gmail.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