All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Sasha Levin <sashal@kernel.org>,
	lkft-triage@lists.linaro.org, Dan Rue <dan.rue@linaro.org>,
	LTP List <ltp@lists.linux.it>,
	open list <linux-kernel@vger.kernel.org>,
	Jan Stancek <jstancek@redhat.com>,
	Basil Eljuse <Basil.Eljuse@arm.com>, chrubis <chrubis@suse.cz>,
	mmarhefk@redhat.com, Netdev <netdev@vger.kernel.org>,
	linux- stable <stable@vger.kernel.org>
Subject: Re: stable-rc-5.3.9-rc1: regressions detected - remove_proc_entry: removing non-empty directory 'net/dev_snmp6', leaking at least 'lo'
Date: Tue, 5 Nov 2019 08:34:59 +0100	[thread overview]
Message-ID: <20191105073459.GB2588562@kroah.com> (raw)
In-Reply-To: <CA+G9fYu+6A3pYQGs2rydYtHNSCf1t9+OTRqrZeCbpc2ARLx2zA@mail.gmail.com>

On Tue, Nov 05, 2019 at 09:44:39AM +0530, Naresh Kamboju wrote:
> Hi Sasha and Greg,
> 
> On Mon, 4 Nov 2019 at 20:59, Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
> >
> > Linux stable rc 5.3 branch running LTP reported following test failures.
> > While investigating these failures I have found this kernel warning
> > from boot console.
> > Please find detailed LTP output log in the bottom of this email.
> >
> > List of regression test cases:
> >   ltp-containers-tests:
> >     * netns_breakns_ip_ipv6_ioctl
> >     * netns_breakns_ip_ipv6_netlink
> >     * netns_breakns_ns_exec_ipv6_ioctl
> >     * netns_breakns_ns_exec_ipv6_netlink
> >     * netns_comm_ip_ipv6_ioctl
> >     * netns_comm_ip_ipv6_netlink
> >     * netns_comm_ns_exec_ipv6_ioctl
> >     * netns_comm_ns_exec_ipv6_netlink
> 
> These reported failures got fixed on latest stable-rc 5.3.y after
> dropping a patch [1].

What is the subject of the patch?

> The kernel warning is also gone now.
> 
> metadata:
>   git branch: linux-5.3.y
>   git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>   git commit: 75c9913bbf6e9e64cb669236571e6af45cddfd68

The -rc tree is rebased all the time, can I get a "real" subject line to
get a chance to figure out what you are trying to refer to here?

> ref:
> [PATCH AUTOSEL 5.3 12/33] blackhole_netdev: fix syzkaller reported issue
> [1] https://lkml.org/lkml/2019/10/25/794

lore.kernel.org is much more reliable :)

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: ltp@lists.linux.it
Subject: [LTP] stable-rc-5.3.9-rc1: regressions detected - remove_proc_entry: removing non-empty directory 'net/dev_snmp6', leaking at least 'lo'
Date: Tue, 5 Nov 2019 08:34:59 +0100	[thread overview]
Message-ID: <20191105073459.GB2588562@kroah.com> (raw)
In-Reply-To: <CA+G9fYu+6A3pYQGs2rydYtHNSCf1t9+OTRqrZeCbpc2ARLx2zA@mail.gmail.com>

On Tue, Nov 05, 2019 at 09:44:39AM +0530, Naresh Kamboju wrote:
> Hi Sasha and Greg,
> 
> On Mon, 4 Nov 2019 at 20:59, Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
> >
> > Linux stable rc 5.3 branch running LTP reported following test failures.
> > While investigating these failures I have found this kernel warning
> > from boot console.
> > Please find detailed LTP output log in the bottom of this email.
> >
> > List of regression test cases:
> >   ltp-containers-tests:
> >     * netns_breakns_ip_ipv6_ioctl
> >     * netns_breakns_ip_ipv6_netlink
> >     * netns_breakns_ns_exec_ipv6_ioctl
> >     * netns_breakns_ns_exec_ipv6_netlink
> >     * netns_comm_ip_ipv6_ioctl
> >     * netns_comm_ip_ipv6_netlink
> >     * netns_comm_ns_exec_ipv6_ioctl
> >     * netns_comm_ns_exec_ipv6_netlink
> 
> These reported failures got fixed on latest stable-rc 5.3.y after
> dropping a patch [1].

What is the subject of the patch?

> The kernel warning is also gone now.
> 
> metadata:
>   git branch: linux-5.3.y
>   git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>   git commit: 75c9913bbf6e9e64cb669236571e6af45cddfd68

The -rc tree is rebased all the time, can I get a "real" subject line to
get a chance to figure out what you are trying to refer to here?

> ref:
> [PATCH AUTOSEL 5.3 12/33] blackhole_netdev: fix syzkaller reported issue
> [1] https://lkml.org/lkml/2019/10/25/794

lore.kernel.org is much more reliable :)

thanks,

greg k-h

  reply	other threads:[~2019-11-05  7:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-04 15:29 stable-rc-5.3.9-rc1: regressions detected - remove_proc_entry: removing non-empty directory 'net/dev_snmp6', leaking at least 'lo' Naresh Kamboju
2019-11-04 15:29 ` [LTP] " Naresh Kamboju
2019-11-05  4:14 ` Naresh Kamboju
2019-11-05  4:14   ` [LTP] " Naresh Kamboju
2019-11-05  7:34   ` Greg Kroah-Hartman [this message]
2019-11-05  7:34     ` Greg Kroah-Hartman
2019-11-05  7:58     ` Naresh Kamboju
2019-11-05  7:58       ` [LTP] " Naresh Kamboju
2019-11-05  8:06       ` Greg Kroah-Hartman
2019-11-05  8:06         ` [LTP] " Greg Kroah-Hartman
2019-11-05  8:39         ` Naresh Kamboju
2019-11-05  8:39           ` [LTP] " Naresh Kamboju

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=20191105073459.GB2588562@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Basil.Eljuse@arm.com \
    --cc=chrubis@suse.cz \
    --cc=dan.rue@linaro.org \
    --cc=jstancek@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=ltp@lists.linux.it \
    --cc=mmarhefk@redhat.com \
    --cc=naresh.kamboju@linaro.org \
    --cc=netdev@vger.kernel.org \
    --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.