From: Eric Biggers <ebiggers@kernel.org>
To: Jessica Yu <jeyu@kernel.org>
Cc: Sasha Levin <sashal@kernel.org>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Alexei Starovoitov <ast@kernel.org>,
stable@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jeff Vander Stoep <jeffv@google.com>,
Kees Cook <keescook@chromium.org>, NeilBrown <neilb@suse.com>
Subject: Re: [PATCH v3 2/5] fs/filesystems.c: downgrade user-reachable WARN_ONCE() to pr_warn_once()
Date: Wed, 18 Mar 2020 15:55:24 -0700 [thread overview]
Message-ID: <20200318225524.GE2334@sol.localdomain> (raw)
In-Reply-To: <20200318150926.GA4144@linux-8ccs>
On Wed, Mar 18, 2020 at 04:09:26PM +0100, Jessica Yu wrote:
> +++ Sasha Levin [17/03/20 22:30 +0000]:
> > Hi
> >
> > [This is an automated email]
> >
> > This commit has been processed because it contains a -stable tag.
> > The stable tag indicates that it's relevant for the following trees: all
> >
> > The bot has tested the following trees: v5.5.9, v5.4.25, v4.19.109, v4.14.173, v4.9.216, v4.4.216.
> >
> > v5.5.9: Build OK!
> > v5.4.25: Build OK!
> > v4.19.109: Build OK!
> > v4.14.173: Build OK!
> > v4.9.216: Failed to apply! Possible dependencies:
> > 41124db869b7 ("fs: warn in case userspace lied about modprobe return")
> >
> > v4.4.216: Failed to apply! Possible dependencies:
> > 41124db869b7 ("fs: warn in case userspace lied about modprobe return")
> >
> >
> > NOTE: The patch will not be queued to stable trees until it is upstream.
> >
> > How should we proceed with this patch?
>
> Since commit 41124db869b7 was introduced v4.13, I guess we should
> change the stable tag to:
>
> Cc: stable@vger.kernel.org # v4.13+
>
It should use:
Fixes: 41124db869b7 ("fs: warn in case userspace lied about modprobe return")
Cc: <stable@vger.kernel.org> # v4.13+
I'll add it.
next prev parent reply other threads:[~2020-03-18 22:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-14 21:34 [PATCH v3 0/5] module autoloading fixes and cleanups Eric Biggers
2020-03-14 21:34 ` [PATCH v3 1/5] kmod: make request_module() return an error when autoloading is disabled Eric Biggers
2020-03-18 16:03 ` Jessica Yu
2020-03-14 21:34 ` [PATCH v3 2/5] fs/filesystems.c: downgrade user-reachable WARN_ONCE() to pr_warn_once() Eric Biggers
2020-03-17 22:30 ` Sasha Levin
2020-03-18 15:09 ` Jessica Yu
2020-03-18 22:55 ` Eric Biggers [this message]
2020-03-18 15:43 ` Jessica Yu
2020-03-18 22:54 ` Eric Biggers
2020-03-14 21:34 ` [PATCH v3 3/5] docs: admin-guide: document the kernel.modprobe sysctl Eric Biggers
2020-03-14 21:34 ` [PATCH v3 4/5] selftests: kmod: fix handling test numbers above 9 Eric Biggers
2020-03-14 21:34 ` [PATCH v3 5/5] selftests: kmod: test disabling module autoloading Eric Biggers
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=20200318225524.GE2334@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=ast@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jeffv@google.com \
--cc=jeyu@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.com \
--cc=sashal@kernel.org \
--cc=stable@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.