3.5.7.6 -stable review patch.  If anyone has any objections, please let me know.

------------------

From: Cong Wang <amw...@redhat.com>

commit 604dfd6efc9b79bce432f2394791708d8e8f6efc upstream.

The return value of pktgen_add_device() is not checked, so
even if we fail to add some device, for example, non-exist one,
we still see "OK:...". This patch fixes it.

After this patch, I got:

        # echo "add_device non-exist" > /proc/net/pktgen/kpktgend_0
        -bash: echo: write error: No such device
        # cat /proc/net/pktgen/kpktgend_0
        Running:
        Stopped:
        Result: ERROR: can not add device non-exist
        # echo "add_device eth0" > /proc/net/pktgen/kpktgend_0
        # cat /proc/net/pktgen/kpktgend_0
        Running:
        Stopped: eth0
        Result: OK: add_device=eth0

(Candidate for -stable)

Cc: David S. Miller <da...@davemloft.net>
Signed-off-by: Cong Wang <amw...@redhat.com>
Signed-off-by: David S. Miller <da...@davemloft.net>
Signed-off-by: Herton Ronaldo Krzesinski <herton.krzesin...@canonical.com>
---
 net/core/pktgen.c |    9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/net/core/pktgen.c b/net/core/pktgen.c
index aa278cd..2a42802 100644
--- a/net/core/pktgen.c
+++ b/net/core/pktgen.c
@@ -1797,10 +1797,13 @@ static ssize_t pktgen_thread_write(struct file *file,
                        return -EFAULT;
                i += len;
                mutex_lock(&pktgen_thread_lock);
-               pktgen_add_device(t, f);
+               ret = pktgen_add_device(t, f);
                mutex_unlock(&pktgen_thread_lock);
-               ret = count;
-               sprintf(pg_result, "OK: add_device=%s", f);
+               if (!ret) {
+                       ret = count;
+                       sprintf(pg_result, "OK: add_device=%s", f);
+               } else
+                       sprintf(pg_result, "ERROR: can not add device %s", f);
                goto out;
        }
 
-- 
1.7.9.5

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to