linux-kernel - Re: linux-next: Tree for Apr 9

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: <CA+icZUXTPe_nT40CG1x9AER+Ctc+zmzFG0YYcpnsXb01_vcWLQ@mail.gmail.com>
Date:	Tue, 9 Apr 2013 17:11:40 +0200
From:	Sedat Dilek <sedat.dilek@...il.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next <linux-next@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for Apr 9

On Tue, Apr 9, 2013 at 4:32 PM, Sedat Dilek <sedat.dilek@...il.com> wrote:
> On Tue, Apr 9, 2013 at 4:23 PM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>> Hi Sedat,
>>
>> On Tue, 9 Apr 2013 16:11:50 +0200 Sedat Dilek <sedat.dilek@...il.com> wrote:
>>>
>>> [ CC Al Viro ]
>>
>> You forgot to do that ...
>>
>>> Is there a "magic" git-command to revert all commits coming from your
>>> latest vfs-merge (commit c1c04d3667608a630ae0821995b465a523e83fb1)?
>>>
>>> 2013-04-09 11:36 Stephen Rothwell   │ M─┐ │ │ │ │ │ │         │ 20130405/vfs
>>
>> You would normally do "git revert -m 1 c1c04d366760". However, that does
>> not revert cleanly in today's linux-next (due to more patches modifying
>> the files involved).
>>
>
> Just wanted to improve my git Know-How.
>
>>> After reverting all these commits I would like to pull-in latest
>>> vfs.git#for-next.
>>
>> It would probably be easier to wait for tomorrow's linux-next.  Or just
>> test Al's tree in its own.
>
> Doug reported problems on his way "reverting the current vfs stuff"
> and Al's new tree was reported as OK.
> A lot of merge-conflicts... that's what I see when trying to pull in
> Al's tree in today's Linux-Next.
> So, I better wait for tommorrow.
>
> Anyway, a warning in your CHANGELOG is very much appreciated on such
> KNOWN ISSUES.
>

vfs-next does break in KVM, cannot say this is due to vfs-related
changes or other stuff.
Build-log attached.
- Sedat -

> Regards,
> - Sedat -
>
>> --
>> Cheers,
>> Stephen Rothwell                    sfr@...b.auug.org.au

View attachment "build-log_3.9.0-rc4-1-vfsnext-small.txt" of type "text/plain" (30357 bytes)