From: Sven Eckelmann <sven@narfation.org>
To: Greg KH <greg@kroah.com>
Cc: b.a.t.m.a.n@lists.open-mesh.org,
Marek Lindner <mareklindner@neomailbox.ch>,
stable@vger.kernel.org
Subject: Re: [B.A.T.M.A.N.] [PATCH 4.7] batman-adv: Fix pagefault during neigh_node free
Date: Mon, 12 Sep 2016 17:21:59 +0200 [thread overview]
Message-ID: <1707606.1cADVqls3C@bentobox> (raw)
In-Reply-To: <20160912145209.GA6452@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 1006 bytes --]
On Montag, 12. September 2016 16:52:09 CEST Greg KH wrote:
> On Tue, Sep 06, 2016 at 09:25:29AM +0200, Simon Wunderlich wrote:
> > From: Marek Lindner <mareklindner@neomailbox.ch>
> >
> > commit d9f179877e50ae2681fe7b0b83e0d9f63b6165ad upstream.
>
> That is not the commit id of this patch :(
>
> What is the real one?
>
> Please be more careful...
Just checked it and it looks like the patch already mentioned in the
"commit xxxxx upstream" line:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d9f179877e50ae2681fe7b0b83e0d9f63b6165ad
I've only rephrased the commit message (see above my signed-off-by line) to
explain why it is a user reported [1] problem. The initial patch didn't
explain this at all and made it look like a simple cleanup change. We
only became aware of the importance of this change after the original
"cleanup" version was accepted by Linus (part of 4.8-rc1 when I remember
correctly).
Kind regards,
Sven
[1] https://www.open-mesh.org/issues/292
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Sven Eckelmann <sven@narfation.org>
To: Greg KH <greg@kroah.com>
Cc: Simon Wunderlich <sw@simonwunderlich.de>,
stable@vger.kernel.org, b.a.t.m.a.n@lists.open-mesh.org,
Marek Lindner <mareklindner@neomailbox.ch>
Subject: Re: [PATCH 4.7] batman-adv: Fix pagefault during neigh_node free
Date: Mon, 12 Sep 2016 17:21:59 +0200 [thread overview]
Message-ID: <1707606.1cADVqls3C@bentobox> (raw)
In-Reply-To: <20160912145209.GA6452@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 1006 bytes --]
On Montag, 12. September 2016 16:52:09 CEST Greg KH wrote:
> On Tue, Sep 06, 2016 at 09:25:29AM +0200, Simon Wunderlich wrote:
> > From: Marek Lindner <mareklindner@neomailbox.ch>
> >
> > commit d9f179877e50ae2681fe7b0b83e0d9f63b6165ad upstream.
>
> That is not the commit id of this patch :(
>
> What is the real one?
>
> Please be more careful...
Just checked it and it looks like the patch already mentioned in the
"commit xxxxx upstream" line:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d9f179877e50ae2681fe7b0b83e0d9f63b6165ad
I've only rephrased the commit message (see above my signed-off-by line) to
explain why it is a user reported [1] problem. The initial patch didn't
explain this at all and made it look like a simple cleanup change. We
only became aware of the importance of this change after the original
"cleanup" version was accepted by Linus (part of 4.8-rc1 when I remember
correctly).
Kind regards,
Sven
[1] https://www.open-mesh.org/issues/292
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-09-12 15:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 7:25 [B.A.T.M.A.N.] [PATCH 4.4] batman-adv: Fix pagefault during neigh_node free Simon Wunderlich
2016-09-06 7:25 ` Simon Wunderlich
2016-09-06 7:25 ` [B.A.T.M.A.N.] [PATCH 4.6] " Simon Wunderlich
2016-09-06 7:25 ` Simon Wunderlich
2016-09-06 7:25 ` [B.A.T.M.A.N.] [PATCH 4.7] " Simon Wunderlich
2016-09-06 7:25 ` Simon Wunderlich
2016-09-12 14:52 ` [B.A.T.M.A.N.] " Greg KH
2016-09-12 14:52 ` Greg KH
2016-09-12 15:21 ` Sven Eckelmann [this message]
2016-09-12 15:21 ` Sven Eckelmann
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=1707606.1cADVqls3C@bentobox \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=greg@kroah.com \
--cc=mareklindner@neomailbox.ch \
--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.