From: Pavel Machek <pavel@denx.de>
To: Amy Fong <Amy_Fong@mentor.com>
Cc: Pavel Machek <pavel@denx.de>,
cip-dev@lists.cip-project.org, nobuhiro1.iwamatsu@toshiba.co.jp
Subject: Re: [cip-dev] [PATCH 4.19.y-cip 1/6] Backport netfilter: nf_tables: autoload modules from the abort path
Date: Tue, 11 Jan 2022 10:02:18 +0100 [thread overview]
Message-ID: <20220111090218.GA22781@amd> (raw)
In-Reply-To: <YdyTRgrErYXoQzti@cat>
[-- Attachment #1: Type: text/plain, Size: 1232 bytes --]
Hi!
> > > Ok, let me take a look at the series. But... could you provide some
> > > kind of explanation of what these are and why you want them in -cip?
> > >
> > > These are not usual "hardware enablement" patches...
> >
> > 0/6 email was not part of the thread, so I missed it in the first
> > look.
> >
> > I see it fixes sysbot report.
> >
> > Do you have special loads where you are hitting these netfilter
> > problems? Are similar fixes needed in 4.4 / 5.10?
> > Would it make sense to get it fixed in -stable kernels?
>
> We haven't been able to reproduce the issue but apparently it's being reproduced
> periodically.
>
> The offending patch doesn't appear in linux-4.4.y-cip
> linux-5.10.y-cip has the fix already.
>
> Both patches were introduced in 5.5.0-rc5
Thank you for answers.
Is there reason not to submit it to stable? You are describing it is
as a bugfix, and Greg takes those. [Advantages are a) community
review, b) less patches to maintain for us, c) bug fixed for everyone,
not just us].
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2022-01-11 9:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <16C8EE09FDEB733D.27414@lists.cip-project.org>
2022-01-10 14:10 ` [cip-dev] [PATCH 4.19.y-cip 1/6] Backport netfilter: nf_tables: autoload modules from the abort path Amy Fong
2022-01-10 17:55 ` Pavel Machek
2022-01-10 18:06 ` Pavel Machek
2022-01-10 20:12 ` Amy Fong
2022-01-11 9:02 ` Pavel Machek [this message]
2022-01-11 14:43 ` Amy Fong
2022-01-11 17:53 ` Pavel Machek
2023-03-10 11:43 ` Jan Kiszka
2023-03-10 14:20 ` Fong, Amy
2022-01-10 14:12 ` [cip-dev] [PATCH 4.19.y-cip 2/6] " Amy Fong
2022-01-10 14:12 ` [cip-dev] [PATCH 4.19.y-cip 3/6] " Amy Fong
2022-01-10 14:13 ` [cip-dev] [PATCH 4.19.y-cip 4/6] " Amy Fong
2022-01-10 14:14 ` [cip-dev] [PATCH 4.19.y-cip 5/6] " Amy Fong
2022-01-10 14:21 ` [cip-dev] [PATCH 4.19.y-cip 6/6] " Amy Fong
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=20220111090218.GA22781@amd \
--to=pavel@denx.de \
--cc=Amy_Fong@mentor.com \
--cc=cip-dev@lists.cip-project.org \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
/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