netdev - Re: [PATCH 0/3] [PATCHSET] netlink error management

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: <20070322195754.GZ521@postel.suug.ch>
Date:	Thu, 22 Mar 2007 20:57:54 +0100
From:	Thomas Graf <tgraf@...g.ch>
To:	David Miller <davem@...emloft.net>
Cc:	netdev@...r.kernel.org, kaber@...sh.net
Subject: Re: [PATCH 0/3] [PATCHSET] netlink error management

* David Miller <davem@...emloft.net> 2007-03-22 12:23
> From: Thomas Graf <tgraf@...g.ch>
> Date: Thu, 22 Mar 2007 00:18:01 +0100
> 
> > This series of patches simplifies the error management and
> > signalization of dump starts of netlink_run_queue() message
> > handlers. It touches a fair bit of nfnetlink code as the
> > error pointer has been passed on to subsystems.
> 
> Thomas can you respin these patches?  They no longer apply
> now that I put your other rtnl_link bits into net-2.6.22

I guess I've posted too many patches series, the patches should
still apply, at least it works in my quilt tree, but depend on
others. The series I've posted in the correct order are:

[RESEND] rtnetlink message handler registration interface
  already applied
 
[RESEND] [NET] rules: Unified rules dumping
  already applied

[PATCH 0/5] [PATCHSET] Netlink Patches
  even though there have been objects because of nfnetlink
  at first, the patches can go in as-is

[NETFILTER] nfnetlink: netlink_run_queue() already checks
                       for NLM_F_REQUEST

[PATCH 0/3] [PATCHSET] netlink error management
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html