[Bug 266048] [ixgbe] 82599ES reports IPv4 UDP with zero checksum as input errors

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=266048

Anthony Capone  changed:

   What|Removed |Added

 CC||cap...@cap1.net

--- Comment #2 from Anthony Capone  ---
I believe I am also affected by this driver bug. I have tried this on a vanilla
Freebsd install and the errors IN are still there... however, I did first
notice this on an OPNsense install. 

See the details here:

https://forum.opnsense.org/index.php?topic=30645

-- 
You are receiving this mail because:
You are the assignee for the bug.

Re: getaddrinfo error for existing host without requested address family

[Mike Karels]

On Wed, 28 Sep 2022, Konstantin Belousov wrote:

> On Tue, Sep 27, 2022 at 03:53:12PM -0500, Mike Karels wrote:
> > I recently noticed the following behavior:
> > 
> > % ping6 redrock
> > ping6: Name does not resolve
> > % host redrock
> > redrock.karels.net has address 10.0.2.2
> > redrock.karels.net mail is handled by 10 mail.karels.net.
> > % ping6 nonexistenthost
> > ping6: Name does not resolve
> > 
> > The first error message is misleading, because the name *does* resolve,
> > but has no  record, and it is the same error message as for a name
> > that truly does not exist.  The problem comes from the set of error
> > codes that getaddrinfo() returns in these two cases.  The problem did
> > not exist with gethostbyname(), which has separate error codes for the
> > two (although gethostbyname did not have provision for IPv6, it handled
> > cases like domain names and mail domains without IPv4 addresses).
> > 
> > getaddrinfo() uses a richer set of error codes than gethostbyname(), but
> > still misses this case.  However, looking at , I see
> > 
> > #if 0
> > /* Obsoleted on RFC 2553bis-02 */
> > #define EAI_ADDRFAMILY   1  /* address family for hostname not 
> > supported */
> > #endif
> > ...
> > #if 0
> > /* Obsoleted on RFC 2553bis-02 */
> > #define EAI_NODATA   7  /* no address associated with hostname 
> > */
> > #endif
> > 
> > I don't know why these two were omitted from the update to RFC 2553, but
> > the first seems to me to be the correct error for an existing name without
> > an address for the requested address family.  Also, that is the error
> > message produced by Linux (Ubuntu 22.04.1).
> > 
> > NetBSD and OpenBSD produce the second of these two errors for a host
> > without the requested address.  But they also produce the same error
> > when a name does not exist.
> > 
> > RFC 2553bis-02 has timed out, and is replaced by RFC 3493, which is also
> > missing EAI_ADDRFAMILY.  These are informational RFCs, not specifying an
> > Internet standard.
> > 
> > I propose re-enabling EAI_ADDRFAMILY and using it for the situation
> > where a name exists but does not have an address in the requested family.
> > This would make the error in the example less misleading, and would behave
> > the same as Linux in this regard.  The change to netdb.h is trivial, but
> > getaddrinfo() needs a little more work because it uses the NS_* errors
> > from  internally and then translates.  But it will benefit
> > from greater accuracy in other cases as well (e.g.  "out of memory"
> > rather than "Name does not resolve").
> > 
> > Comments?  I have a change in progress, but wanted to float the idea
> > before I finish it and put it into review.

> Perhaps look there
> https://www.openwall.com/lists/libc-coord/2022/09/27/1

> You might want to participate in the thread, instead of me.

I participated in a short discussion on that list.  The TL;DR:

- Linux/glibc (Ubuntu at least) uses EAI_NODATA ("No address associated
with hostname") when a name is valid but does not have the requested
address family.  This is better than FreeBSD currently, as it is
distinguished from EAI_NONAME ("Name or service not known").  But it
implies that there is no address in any family.  (I showed an example
from ping6 above, but it turns out to be atypical.)

- The author of the musl C library for Linux plans to use EAI_NODATA as
well, but with a different error message.

- Linux also uses EAI_ADDRFAMILY, but only when a numeric address is in the
wrong family, e.g. telnet -6 127.0.0.1.

- POSIX, like the latest RFC, does not define EAI_NODATA or EAI_ADDRFAMILY.

- There were no other opinions expressed.

I see two choices for FreeBSD when there is no address in the requested
family.  One is to use EAI_NODATA, probably using a modified error message.
The has the main disadvantage that we have several NLS translations.  Also,
it is different than Linux.

The other choice is to use EAI_ADDRFAMILY ("Address family for hostname
not supported") as originally proposed.  The existing error message seems
reasonable for this case.

Any comments or votes?  I am inclined to use EAI_ADDRFAMILY as originally
proposed.

Mike

[Bug 184311] [bge] [panic] kernel panic with bge(4) on SunFire X2100

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=184311

Graham Perrin  changed:

   What|Removed |Added

   Keywords||crash

--- Comment #9 from Graham Perrin  ---
Keyword: 

crash

– in lieu of summary line prefix: 

[panic]

* bulk change for the keyword
* summary lines may be edited manually (not in bulk). 

Keyword descriptions and search interface: 



-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 138782] [panic] sbflush_internal: cc 0 || mb 0xffffff004127b000 || mbcnt 2304

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=138782

Graham Perrin  changed:

   What|Removed |Added

   Keywords||crash

--- Comment #9 from Graham Perrin  ---
Keyword: 

crash

– in lieu of summary line prefix: 

[panic]

* bulk change for the keyword
* summary lines may be edited manually (not in bulk). 

Keyword descriptions and search interface: 



-- 
You are receiving this mail because:
You are the assignee for the bug.

[Bug 121774] [swi] [panic] 6.3 kernel panic in swi1: net

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=121774

Graham Perrin  changed:

   What|Removed |Added

   Keywords||crash

--- Comment #6 from Graham Perrin  ---
Keyword: 

crash

– in lieu of summary line prefix: 

[panic]

* bulk change for the keyword
* summary lines may be edited manually (not in bulk). 

Keyword descriptions and search interface: 



-- 
You are receiving this mail because:
You are the assignee for the bug.

Netlink and vnet

[Doug Rabson]

In Linux container runtimes, typically netlink is used with network
namespaces to manage the interfaces and addresses for a container. This
typically involves briefly joining the network namespace to perform actions
like socket(AF_NETLINK, ...).

It would be nice to find a similar approach on FreeBSD to replace the
'jexec ifconfig ...' approach which I'm using now. Is there any way to get
a netlink socket that connects to a specific vnet? This would be cleaner,
more efficient and would simplify porting the Linux runtimes to FreeBSD.

Re: Help wanted with MFC 256820

[Hans Petter Selasky]

On 10/17/22 01:59, Koichiro Iwao wrote:

On Sun, Oct 16, 2022 at 06:12:40PM +0200, Hans Petter Selasky wrote:


Hi,

I think you should do:

git cherry-pick -x 9823a0c0acf4fc277a71336ea737e1de7c65742f

Then:

git commit --amend

And remove the "MFC after" tag.

Then push it to stable/13 . You maybe need to specify the override authors
flag before pushing.

--HPS


Hi Hans,

Thanks for the advice. Do you mean you have approved me to do that?



Send me the "git show" output of the commit before you push it, and I'll 
review it for you.


--HPS