All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: <Claudiu.Beznea@microchip.com>
Cc: <Nicolas.Ferre@microchip.com>, <netdev@vger.kernel.org>
Subject: Re: macb: inconsistent Rx descriptor chain after OOM
Date: Mon, 16 Sep 2019 12:14:11 +0200	[thread overview]
Message-ID: <mvmmuf4fszw.fsf@suse.de> (raw)
In-Reply-To: <51458d2e-69a5-2a30-2167-7f47a43d9a2f@microchip.com> (Claudiu Beznea's message of "Mon, 16 Sep 2019 10:00:27 +0000")

On Sep 16 2019, <Claudiu.Beznea@microchip.com> wrote:

> I will have a look on it. It would be good if you could give me some
> details about the steps to reproduce it.

You need to trigger OOM.

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

  reply	other threads:[~2019-09-16 10:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-16  7:41 macb: inconsistent Rx descriptor chain after OOM Andreas Schwab
2019-09-16 10:00 ` Claudiu.Beznea
2019-09-16 10:14   ` Andreas Schwab [this message]
2019-09-16 10:16     ` Claudiu.Beznea
2019-09-25 10:05       ` Harini Katakam

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=mvmmuf4fszw.fsf@suse.de \
    --to=schwab@suse.de \
    --cc=Claudiu.Beznea@microchip.com \
    --cc=Nicolas.Ferre@microchip.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.