On Wed, Dec 07, 2016 at 06:49:06AM +, Jason McIntyre wrote:
> On Mon, Dec 05, 2016 at 02:05:02PM -0800, Bryan Vyhmeister wrote:
> > In responding to a post on misc@, I noticed that bioctl(8) uses all sd(4)
> > devices in the examples sections while softraid(4) uses wd(4) devices
> > for the chu
On Mon, Dec 05, 2016 at 02:05:02PM -0800, Bryan Vyhmeister wrote:
> In responding to a post on misc@, I noticed that bioctl(8) uses all sd(4)
> devices in the examples sections while softraid(4) uses wd(4) devices
> for the chunks. This patch updates softraid.4 to use sd(4) devices as
> well. I hav
On Mon, Nov 28, 2016 at 03:28:40PM +0100, Martin Pieuchot wrote:
> These chunks depend on the if_attach() bits I sent in the previous
> email. As soon as if_attach() always raise the ipl level to IPL_SOFTNET
> pfi_attach_ifnet() doesn't need to do it.
>
> The rest is already safe since hooks are
On Mon, Nov 28, 2016 at 03:24:56PM +0100, Martin Pieuchot wrote:
> This remove all but one splsoftnet() recursions when creating or
> destroying cloned interfaces.
>
> Note that I have to introduce some extra splsoftnet()/splx() dances in
> tun(4) and tap(4) create functions.
switchopen() also ca
On Mon, Nov 28, 2016 at 03:08:20PM +0100, Martin Pieuchot wrote:
> umb(4) also calls in_ioctl() directly but always under splnet(), so for
> the moment this is good enough.
>
> ok?
OK bluhm@
>
> Index: netinet/igmp.c
> ===
> RCS fi
On Mon, Nov 28, 2016 at 03:36:04PM +0100, Martin Pieuchot wrote:
> This is now always called at IPL_SOFTNET, so assert it.
>
> ok?
OK bluhm@
>
> Index: net/route.c
> ===
> RCS file: /cvs/src/sys/net/route.c,v
> retrieving revision
On Mon, Nov 28, 2016 at 04:01:14PM +0100, Martin Pieuchot wrote:
> @@ -313,7 +319,13 @@ bpf_detachd(struct bpf_d *d)
> int error;
>
> d->bd_promisc = 0;
> +
> + bpf_get(d);
> + mtx_leave(&d->bd_mtx);
> error = ifpromisc(bp->bif_if
On 2016/12/06 19:46, Adam Wolk wrote:
> Diff follows. On a side note it would be nice to have a OpenBSD-release
> shorthand on man.openbsd.org pointing to the latest release. That would help
> avoid a similar diff churn after 6.1 gets released.
It sounds like it should be simple, but there is a pr
On Tue, Dec 06, 2016 at 07:46:31PM +0100, Adam Wolk wrote:
> Hi tech@
>
> _gypcio on IRC reported that pkg_sign uses a -s signify flag that was renamed
> in
> -current to signify2. The entry in the FAQ showing that example also linked
> to a
> pkg_sign man page from -current which lead to the co
On Tue, Dec 06, 2016 at 08:01:12PM +0100, Adam Wolk wrote:
> On a side note it would be nice to have a OpenBSD-release shorthand on
> man.openbsd.org pointing to the latest release. That would help avoid
> a similar diff churn after 6.1 gets released.
Although I recognize my opinion does not carry
On Tue, Dec 06, 2016 at 07:46:31PM +0100, Adam Wolk wrote:
> Hi tech@
>
> _gypcio on IRC reported that pkg_sign uses a -s signify flag that was renamed
> in
> -current to signify2. The entry in the FAQ showing that example also linked
> to a
> pkg_sign man page from -current which lead to the co
Hi tech@
_gypcio on IRC reported that pkg_sign uses a -s signify flag that was renamed in
-current to signify2. The entry in the FAQ showing that example also linked to a
pkg_sign man page from -current which lead to the confusion.
Here is a diff generated with:
perl -pi.bak -e
's|man.openbsd.
Stefan Sperling writes:
> On Thu, Dec 01, 2016 at 07:48:07PM +0100, Stefan Sperling wrote:
>> This diff adds mira support to the iwn(4) driver.
>>
>> I have tested this with:
>> iwn0 at pci2 dev 0 function 0 "Intel WiFi Link 5100" rev 0x00: msi, MIMO 1T2R
>> When reporting test results please me
On Tue, Nov 29, 2016 at 05:03:44PM +0100, Martin Pieuchot wrote:
> Diff below removes the 'struct route_in6' argument from in6_selectsrc().
>
> It is only used by in6_pcbselsrc() so move the code there. This reduces
> differences with IPv4 and help me to get rid of 'struct route*'.
This changes
Patrick Wildt writes:
> Hi,
>
> If the BROADCAST flag is set on a BOOTREPLY, the RFC specifies that
> we SHOULD forward the packet not only as L3 broadcast, but also as
> L2 broadcast. Apparently that helps on older machines that can't
> handle L2 unicast replies.
>
> ok?
ok jca@
> Patrick
>
>
On 2016/12/05 17:21, Okan Demirmen wrote:
> Thanks; I didn't realize there'd be trouble, else I would have published
> something like this along with the change (one small mistake on my part
> below, fixing...).
Here's a sed script that seems to do the trick. Should we put it somewhere
(upgrade no
On Thu, Dec 01, 2016 at 07:48:07PM +0100, Stefan Sperling wrote:
> This diff adds mira support to the iwn(4) driver.
>
> I have tested this with:
> iwn0 at pci2 dev 0 function 0 "Intel WiFi Link 5100" rev 0x00: msi, MIMO 1T2R
> When reporting test results please mention which device was tested.
>
17 matches
Mail list logo
