netdev - Re: [PATCHv1 net-next 0/5] netlink: mmap: kernel panic and some issues

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20150812.163819.620222685130362816.davem@davemloft.net>
Date:	Wed, 12 Aug 2015 16:38:19 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	chamaken@...il.com
Cc:	netdev@...r.kernel.org, fw@...len.de
Subject: Re: [PATCHv1 net-next 0/5] netlink: mmap: kernel panic and some
 issues

From: Ken-ichirou MATSUZAWA <chamaken@...il.com>
Date: Wed, 12 Aug 2015 17:28:24 +0900

> It would be better if someone else is working on this.
> Or could you help me out? It's a tough work for me.

If you are fixing a panic, you must show that panic message
and describe in detail the exact sequence of events and state
that lead to that crash.  And then also exactly why your fix
takes care of the problem, and why it is the proper way to
approach the issue.

As-is, your commit message and this top-level introductory
posting are way too terse and I myself can't even figure out
what exactly the purpose of this series is, and what bug it
is precisely fixing.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html