From: David Miller <davem@davemloft.net>
To: mahesh@bandewar.net
Cc: j.vosburgh@gmail.com, andy@greyhouse.net, vfalico@gmail.com,
netdev@vger.kernel.org, edumazet@google.com, maheshb@google.com
Subject: Re: [PATCH net] bonding: avoid possible dead-lock
Date: Wed, 26 Sep 2018 20:24:37 -0700 (PDT) [thread overview]
Message-ID: <20180926.202437.1560312240690479409.davem@davemloft.net> (raw)
In-Reply-To: <20180924214011.234426-1-mahesh@bandewar.net>
From: Mahesh Bandewar <mahesh@bandewar.net>
Date: Mon, 24 Sep 2018 14:40:11 -0700
> From: Mahesh Bandewar <maheshb@google.com>
>
> Syzkaller reported this on a slightly older kernel but it's still
> applicable to the current kernel -
...
> Signed-off-by: Mahesh Bandewar <maheshb@google.com>
Applied and queued up for -stable.
prev parent reply other threads:[~2018-09-27 9:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-24 21:40 [PATCH net] bonding: avoid possible dead-lock Mahesh Bandewar
2018-09-27 3:24 ` David Miller [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=20180926.202437.1560312240690479409.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andy@greyhouse.net \
--cc=edumazet@google.com \
--cc=j.vosburgh@gmail.com \
--cc=mahesh@bandewar.net \
--cc=maheshb@google.com \
--cc=netdev@vger.kernel.org \
--cc=vfalico@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;
as well as URLs for NNTP newsgroup(s).