linux-kernel - Re: [PATCH 7/7] check for O_NONBLOCK in all read

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]

Date:	Wed, 17 Sep 2014 11:33:35 -0400
From:	Milosz Tanski <milosz@...in.com>
To:	Benjamin LaHaise <bcrl@...ck.org>
Cc:	"Theodore Ts'o" <tytso@....edu>,
	Dave Chinner <david@...morbit.com>,
	Jeff Moyer <jmoyer@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Christoph Hellwig <hch@...radead.org>,
	"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
	linux-aio@...ck.org, Mel Gorman <mgorman@...e.de>,
	Volker Lendecke <Volker.Lendecke@...net.de>,
	Tejun Heo <tj@...nel.org>
Subject: Re: [PATCH 7/7] check for O_NONBLOCK in all read_iter instances

On Wed, Sep 17, 2014 at 9:56 AM, Benjamin LaHaise <bcrl@...ck.org> wrote:
> On Wed, Sep 17, 2014 at 09:47:02AM -0400, Theodore Ts'o wrote:
> ...
>> % git version
>> git version 2.1.0
>>
>> Perhaps you and other people are using your own scripts, and not using
>> git send-email?
>
> That would be because none of my systems have git 2.1.0 on them.  Fedora
> (and EPEL) appear to still be back on git 1.9.3 which does not have git
> send-email.  Until that command is more widely propagated, I expect we'll
> see people making this mistake every once in a while.
>
>                 -ben
> --
> "Thought is the essence of where you are now."

My workflow has been to use git format-patch (1.7.9.5 was shipped with
my distro), edit the cover letter then use and mutt to send the
generated emails. Before that I used git apply to import the patches
that Christoph sent me. I thought about it too, but hand editing the
email generated by format-patch to essentially having me take credit
for this sounded like a shady thing to do. The updated version of
git's (2.1.0) format-patch doesn't change the from email address field
either.

The submitting patches document doesn't really describe what to do if
you take patches / collaborate with somebody else or how to credit the
original author. It only deals with the case of a subsystem
maintainers editing the submitters code to fix it up.

All that aside, if somebody has a clear workflow that ensures this
doesn't happen I'm more then willing to follow it.

-- 
Milosz Tanski
CTO
16 East 34th Street, 15th floor
New York, NY 10016

p: 646-253-9055
e: milosz@...in.com
--
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/