linux-kernel - Re: [PATCH] rpc: fix garbage in printk in svc_tcp

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] [day] [month] [year] [list]

Date:	Thu, 20 Sep 2007 16:21:56 -0400
From:	"J. Bruce Fields" <bfields@...ldses.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Wolfgang Walter <wolfgang.walter@...dentenwerk.mhn.de>,
	Neil Brown <neilb@...e.de>, Trond Myklebust <trond@...app.com>,
	stable@...nel.org
Subject: Re: [PATCH] rpc: fix garbage in printk in svc_tcp_accept()

On Thu, Sep 20, 2007 at 01:15:05PM -0700, Linus Torvalds wrote:
> 
> 
> On Thu, 20 Sep 2007, J. Bruce Fields wrote:
> >
> > we upgraded the kernel of a nfs-server from 2.6.17.11 to 2.6.22.6. Since
> > then we get the message
> ...
> 
> Bruce - you're losing authorship information.

Whoops, yes, I usually rely on git-send-email to do that, but was
sending the patch by hand this time in a hurry, reading the commit into
my mail client, and forgot the From: line.  Thanks for catching that.

> So that "always explicitly say who the author is" is a good idea, but when 
> forwarding somebody elses patch, it's *more* than a good idea - at that 
> point it's absolutely required for proper attribution.

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