netdev - Re: BUG: unable to handle kernel paging request at 00000000d8be176d

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: <20120706.012921.1688197243231281609.davem@davemloft.net>
Date:	Fri, 06 Jul 2012 01:29:21 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	wfg@...ux.intel.com
Cc:	eric.dumazet@...il.com, netdev@...r.kernel.org,
	steffen.klassert@...unet.com
Subject: Re: BUG: unable to handle kernel paging request at 00000000d8be176d

From: Fengguang Wu <wfg@...ux.intel.com>
Date: Fri, 6 Jul 2012 15:52:45 +0800

> On Fri, Jul 06, 2012 at 03:37:45PM +0800, Fengguang Wu wrote:
>> Hi David,
>> 
>> > Fengguang Wu can I ask you politely not to quote the quilty patch in
>> > it's entirety when reporting bugs?  That screws up my workflow because
>> > that patch goes then gets installed as a new patch in patchwork and I
>> > have to therefore tick it off every time you report a bug.
>> 
>> Sorry for that!  Is it fine to _attach_ the referenced patch, or just
>> a raw diff?  Or, the commit SHA and subject are all you want to see?
> 
> I used git-format-patch which makes a formal patch. How about git-show?
> The output will be less like a formal patch, for example:

No patch, in any format.

It's completely pointless to attach the diff, anyone can use the
commit log message and SHA ID to fetch the patch if they want.

It's redundancy therefore also makes it a huge waste of bandwidth.  I
have no idea why you provide it in the first place.
--
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