linux-kernel - Re: [GIT PULL REQUEST] md updates for 4.3

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]

Message-ID: <CA+55aFwM2e9sTVtYjrnPjh5RsZafBXbJ5FFYkYi730ojOn+8-w@mail.gmail.com>
Date:	Sat, 5 Sep 2015 18:03:48 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Neil Brown <neil@...wn.name>
Cc:	"linux-raid@...r.kernel.org" <linux-raid@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Goldwyn Rodrigues <rgoldwyn@...e.com>,
	Guoqing Jiang <gqjiang@...e.com>,
	Lidong Zhong <ldzhong@...e.com>,
	Sasha Levin <sasha.levin@...cle.com>,
	Ard Biesheuvel <ard.biesheuvel@...aro.org>,
	Markus Stockhausen <stockhausen@...logia.de>,
	Yi Zhang <yizhan@...hat.com>,
	Benjamin Randazzo <benjamin@...dazzo.fr>
Subject: Re: [GIT PULL REQUEST] md updates for 4.3

On Sat, Sep 5, 2015 at 2:37 AM, Neil Brown <neil@...wn.name> wrote:
>
> Please pull these updates.  I've already merged with the 'block' tree
> to resolve a few simple conflicts.

So for the future, I actually prefer to see and handle the conflicts myself.

I really just prefer knowing what's going on, and merge conflicts are
an indication of cross-maintainer issues which are *exactly* the kinds
of things I want to be aware of.

However, in this case I was "ok, I've already done several other merge
resolutions with the wbole damn bio_endio error handling changes", so
I felt I was aware enough about how that ended up being a
cross-subsystem conflict, and just took your pre-merged version.

If you feel that the conflicts are particularly subtle, or just
generally worry about the merge, or just because you want to do some
merge-testing, what some people end up doing is to send me their
unmerged branch, and then send me a separate ".. and here's the merge
I did". I'll then do the merge myself anyway, but then after doing the
merge I'll switch to a temporary testing branch and re-do the  merge
with the pre-merged state just to verify. Generally the end result is
identical, but when it isn't, that's actually usually interesting
(sometimes it's just a ordering difference, but sometimes it's a merge
error - and so far I think most merge errors have come from
sub-maintainers, for the simple reason that they generally aren't as
used to merging as I am - so even if they know the code better, I
sometimes catch merge gotcha's better).

Thanks,
                          Linus
--
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/