linux-kernel - Re: [PATCHSET] nfs endianness annotations

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

Date:	Thu, 19 Oct 2006 10:31:38 +1000
From:	Neil Brown <neilb@...e.de>
To:	Trond Myklebust <trond.myklebust@....uio.no>
Cc:	Al Viro <viro@....linux.org.uk>, linux-kernel@...r.kernel.org
Subject: Re: [PATCHSET] nfs endianness annotations

On Wednesday October 18, trond.myklebust@....uio.no wrote:
> On Tue, 2006-10-10 at 04:09 +0100, Al Viro wrote:
> > Series below does endianness annotations of nfs and nfsd; it had been
> > sitting in my tree for quite a while.  In part it's based on Alexey's
> > patches.
> > 
> > I thought to hold it back until the next merge window, but since we
> > do get new breakage that would be instantly caught by endianness checks...
> > IMO it makes sense to see if that puppy could be merged at this point.
> > In any case, the first patch in series is absolutely needed - it's
> > fixing a genuine recently introduced bug.
> 
> Hi Al,
> 
> ACK on patches # 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12. I'd be quite happy
> to get those into mainline ASAP.
> 
> I'll defer to Neil for the rest.

Thanks for the reminder Trond.

Yes, 

Acked-By: NeilBrown <neilb@...e.de>

for 1, 13-25.
Thanks for doing this - there are some important cleanups in there,
particular the clear differentiation between err and host_err (not to
mention the bug fixes!).

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