linux-ext4 - Re: Ext4-patch-queue rebased to 2.6.26-rc1?

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:	Wed, 30 Jul 2008 15:04:12 -0400
From:	Theodore Tso <tytso@....edu>
To:	Gary Hawco <ghawco@....net>
Cc:	"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>
Subject: Re: Ext4-patch-queue rebased to 2.6.26-rc1?

On Wed, Jul 30, 2008 at 09:46:39AM +0000, Gary Hawco wrote:
> 
> The latest patch in the queue errors out with "patch already applied"
> error. I noticed that the patch from 073008/0301hrs GMT was rebased against
> 2.6.26-rc1, as opposed to what I think you meant, 2.6.27-rc1. I am sure
> this is why the newest patch from today @ 0339hrs fails to patch the
> 2.6.27-rc1 kernel source cleanly.

That was a typo in the series file, which I have since fixed and
pushed out, but I didn't need to change any of the patches; the
patches all applied to a clean 2.6.27-rc1 kernel, at least when I was
using the 2.6.27-rc1 from git and using "guilt push -a" to apply the
patches (which is how I normally do thigs.)  Do you know which patch
was giving the "patch already applied" error; how are you applying the
patches?

There was a problem in the patch queue that wasn't fixed until "Add
missing patch, ext4__update_documentation..." where the patch queue
was *missing* a patch due to me fumble fingering a git commit.  Maybe
that's what you ran into?  It's since been fixed....

> P.S. I have a minor, weird problem involving midnight commander in both
> Gentoo & Slackware that is also ext4-patch-queue related. The previous
> patch I was using from 071508/2315hrs was fine. I didn't want to use the
> git kernel, so I didn't update until the 072808/0005hrs GMT snapshot (Add
> documentation re: mke2fs.conf label). This snapshot (and presumably all
> newer ones add a continous row of symbols that resemble a nine (9) with a
> longer tail to the border, top & bottom, left & right to mc in both Gentoo
> & Slackware. This is while running in init3. It doesn't do it while running
> in kde and opening a console and then starting mc.

Does that occur with 2.6.27-rc1 without the ext4 patch queue?  That
sounds like terminfo problem or maybe some kind of console font issue.

What happens if you are running with X, and switching to the VC
console via cotrol-alt-f1, and then logging into the VC console?  I'm
not seeing it when I run mc from a vt console on my Ubuntu system,
which I assume is the same as what you are seeing when are using mc
under init 3 on Slackware.

					- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html