On Sun, Oct 30, 2022 at 5:12 PM J. Hannken-Illjes wrote:
>
> > On 30. Oct 2022, at 06:52, Michael van Elst wrote:
> >
> > ozak...@netbsd.org (Ryota Ozaki) writes:
> >
> >> I've committed a possible fix. Could you try it?
> >
> >> Thanks,
> >> ozaki-r
> >
> >
> > I just got a NULL pointer
On Sun, Oct 30, 2022 at 2:52 PM Michael van Elst wrote:
>
> ozak...@netbsd.org (Ryota Ozaki) writes:
>
> >I've committed a possible fix. Could you try it?
>
> >Thanks,
> > ozaki-r
>
>
> I just got a NULL pointer dereference in tcp_ctloutput where
> the previous check for inp == NULL is also
> On 30. Oct 2022, at 06:52, Michael van Elst wrote:
>
> ozak...@netbsd.org (Ryota Ozaki) writes:
>
>> I've committed a possible fix. Could you try it?
>
>> Thanks,
>> ozaki-r
>
>
> I just got a NULL pointer dereference in tcp_ctloutput where
> the previous check for inp == NULL is also
ozak...@netbsd.org (Ryota Ozaki) writes:
>I've committed a possible fix. Could you try it?
>Thanks,
> ozaki-r
I just got a NULL pointer dereference in tcp_ctloutput where
the previous check for inp == NULL is also missing.
[ 24837.756043] fp c0016794db70 tcp_ctloutput() at
Hi,
I've committed a possible fix. Could you try it?
Thanks,
ozaki-r
On Sun, Oct 30, 2022 at 12:17 AM Thomas Klausner wrote:
>
> Hi!
>
> A couple hours later, my shell was in an NFS mounted directory (probably idle
> for some time) and I tried tab-completing an entry, and it panicked
Hi!
A couple hours later, my shell was in an NFS mounted directory (probably idle
for some time) and I tried tab-completing an entry, and it panicked again.
Same location as below.
Hand copied:
tcp_shutdown_wrapper+0x20
nfs_disconnect+0x69
nfs_reconnect+0x1a
nfs_request+0x7fb
nfs_access+0x1ed
Hi!
I’ve upgraded from 9.99.100 (stable) to 9.99.104 this morning (kernel + user
land, but packages still the old ones built on 9.99.100 in case it matters).
A couple hours later I started transmission-gtk and the machine immediately
panicked.
Hand copied:
uvm_fault(0xf8b04ab6d8f0, 0x0,
