Приглашаем к публикации [РИНЦ]

[Среда]

___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 251736] [panic] memcpy_erms general protection fault on AMD Zen 3 (Ryzen 5000 series)

[bugzilla-noreply]

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

--- Comment #12 from Greg V  ---
Now testing upstream OpenZFS:

- 2.0.0-rc1 + compat fixes (cherry-pick 01a65c58 f6bb7c029) = stable
- 2.0.0-rc2 + INVARIANTS + compat fixes = FPU crash
- 2.0.0-rc2 + INVARIANTS + compat fixes + FPU fix (e0716250bf) = unstable
- 2.0.0-rc7 + INVARIANTS + FPU fix = stable
- master + INVARIANTS = stable
- master = stable

(my stability test being running rm -rf /usr/obj/usr and buildkernel a few
times while zpool scrub is going on)

Conclusion: seems like that problem has been fixed upstream. Whatever it was.
I'm not seeing anything obvious in the commit log o_0

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 251736] [panic] memcpy_erms general protection fault on AMD Zen 3 (Ryzen 5000 series)

[bugzilla-noreply]

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

--- Comment #13 from Konstantin Belousov  ---
(In reply to Greg V from comment #12)
What is 'FPU fix (e0716250bf)' ? I am unable to find the hash in openzfs repo.
I am sure nothing like 'fpu fix' was committed to freebsd.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 251736] [panic] memcpy_erms general protection fault on AMD Zen 3 (Ryzen 5000 series)

[bugzilla-noreply]

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

--- Comment #14 from Greg V  ---
(In reply to Konstantin Belousov from comment #13)

https://github.com/openzfs/zfs/commit/e0716250bf34159082d96f04200063e3edb114b6

It was committed yesterday. Apparently authored by you :)

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 251727] [sound] [snd_hda] After update to r368166 no sound recording with internal microphone

[bugzilla-noreply]

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

Matthias Apitz  changed:

   What|Removed |Added

   Severity|Affects Only Me |Affects Some People

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 251727] [sound] [snd_hda] After update to r368166 no sound recording with internal microphone

[bugzilla-noreply]

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

--- Comment #2 from Matthias Apitz  ---
The issue was reproduced by others on the same hardware Acer C720, see
freebsd-current@

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 239561] sysrc prints incorrect values for variables with trailing newlines

[bugzilla-noreply]

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

--- Comment #1 from Devin Teske  ---
Thanks, I'll have a go at fixing this and will raise a differential

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 239560] sysrc misinterprets "variable=value"-like strings as real assignments

[bugzilla-noreply]

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

--- Comment #1 from Devin Teske  ---
Thanks for the report, I'll have a go at fixing it to produce the expected
results

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 251767] wcswidth() from libc reports wrong string lenght (no unicode 9 support)

[bugzilla-noreply]

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

Bug ID: 251767
   Summary: wcswidth() from libc reports wrong string lenght (no
unicode 9 support)
   Product: Base System
   Version: 12.2-STABLE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Many People
  Priority: ---
 Component: bin
  Assignee: b...@freebsd.org
  Reporter: dmil...@me.com

Basically any emoji character from UTF-8 like "👌" is incorrectly reported as
length "1" by wcswidth(const wchar_t *pwcs, size_t n);

Seems like libc in FreeBSD supports older version of Unicode standard than 9?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 251767] wcswidth() from libc reports wrong string lenght (no unicode 9 support)

[bugzilla-noreply]

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

Yuri Pankov  changed:

   What|Removed |Added

 CC||b...@freebsd.org,
   ||yur...@freebsd.org
 Status|New |Open
   Assignee|b...@freebsd.org|yur...@freebsd.org

--- Comment #1 from Yuri Pankov  ---
It's not exactly about unicode support, rather about the character width data
being very outdated.  I have (hopefully) fixed this in -CURRENT, see base
r368390.  I'll check if it's possible to MFC shortly.  As a really quick fix,
try replacing tools/tools/locale/etc/final-maps/widths.txt with the one from
-CURRENT
(https://svnweb.freebsd.org/base/head/tools/tools/locale/etc/final-maps/widths.txt?view=log)
and rebuilding/installing ctype data in share/ctypedefs.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 251770] /bin/sh: false expansion

[bugzilla-noreply]

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

Bug ID: 251770
   Summary: /bin/sh: false expansion
   Product: Base System
   Version: 12.1-STABLE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: bin
  Assignee: b...@freebsd.org
  Reporter: stef...@sdaoden.eu

Hi.

On 11.2 and 12.1 i get false expansion for

  /bin/sh -c 'du=ich wir='"'"'hey '"'"'$du; echo $wir'

It echos hey but should echo "hey ich".

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 244906] kernel booted by loader.efi on VMware Fusion crashes in EFI firmware

[bugzilla-noreply]

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

--- Comment #13 from Graham Perrin  ---
(In reply to Roger Leigh from comment #7)

Also: 

HP Elitebook 830 G7


-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 251775] bsdgrep: egrep regards '{foo}' as invalid regular expression

[bugzilla-noreply]

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

Bug ID: 251775
   Summary: bsdgrep: egrep regards '{foo}' as invalid regular
expression
   Product: Base System
   Version: CURRENT
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: bin
  Assignee: b...@freebsd.org
  Reporter: y...@utahime.org
CC: kev...@freebsd.org

I'm the maintainer of security/logcheck port. It detects log messages that
should be reported by applying regular expressions to each messages with egrep.

After grep is switched to bsdgrep on 13-CURRENT I noticed logcheck produces
some errors caused by egrep. I investigate them and found most of them happens
because regular expressions are invalid according to the definition on
re_format(7). But I also found there is one case that caused by bug of bsdgrep.

In re_format(7) 'bound' is defined as following.

"A bound is '{' followed by an unsigned decimal integer, possibly followed by
',' possibly followed by another unsigned decimal integer, always followed by
'}'.  The integers must lie between 0 and RE_DUP_MAX (255) inclusive, and if
there are two of them, the first may not exceed the second."

And there is also following clarification.

" A '{' followed by a character other than a digit is an ordinary character,
not the beginning of a bound. "

So '{100}' is regarded as bound and therefore is invalid as regular expression.
But '{foo}' isn't regarded as bound. Hence it's a valid regular expression and
matches itself.

Gnugrep's egrep works fine with this regular expression.

--
yasu@eastasia[1575]% uname -U
1202000
yasu@eastasia[1614]% type egrep
egrep is /usr/bin/egrep
yasu@eastasia[1615]% egrep --version
egrep (GNU grep) 2.5.1-FreeBSD

Copyright 1988, 1992-1999, 2000, 2001 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

yasu@eastasia[1616]% echo '{foo}' | egrep '{foo}'
{foo}
yasu@eastasia[1617]%
--

But bsdgrep's egrep results in error.

--
yasu@rolling-vm-freebsd1[1135]% uname -U
1300131
yasu@rolling-vm-freebsd1[1142]% type egrep
egrep is /usr/bin/egrep
yasu@rolling-vm-freebsd1[1143]% egrep --version
egrep (BSD grep, GNU compatible) 2.6.0-FreeBSD
yasu@rolling-vm-freebsd1[1144]% echo '{foo}' | egrep '{foo}'
egrep: repetition-operator operand invalid
yasu@rolling-vm-freebsd1[1145]%
--

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 251775] bsdgrep: egrep regards '{foo}' as invalid regular expression

[bugzilla-noreply]

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

Yuri Pankov  changed:

   What|Removed |Added

 CC||yur...@freebsd.org

--- Comment #1 from Yuri Pankov  ---
It's not grep itself, it's our regex implementation.

POSIX says it's UB:

*+?{
The asterisk, plus-sign, question-mark, and left-brace shall be special
except when used in a bracket expression. Any of the following uses produce
undefined results:
- If a left-brace is not part of a valid interval expression

re_format(7) is free interpretation of the standard.

FWIW, the best way is to fix your regular expressions.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 251775] bsdgrep: egrep regards '{foo}' as invalid regular expression

[bugzilla-noreply]

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

--- Comment #2 from Kyle Evans  ---
(In reply to Yuri Pankov from comment #1)

+1 for fixing (+ upstreaming) it to be POSIX compliant

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 251775] bsdgrep: egrep regards '{foo}' as invalid regular expression

[bugzilla-noreply]

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

--- Comment #3 from Yasuhiro KIMURA  ---
(In reply to Yuri Pankov from comment #1)

Thanks for explanation. Then please let me ask one more question.

While investigating I also found following two patterns are accepted by gnugrep
but rejected bsdgrep.

* '(foo|)'
* '.{0,256}'

According to re_format(7) both of them are invalid as regular expression. Then
are they also invalid with POSIX standard?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 251775] bsdgrep: egrep regards '{foo}' as invalid regular expression

[bugzilla-noreply]

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

--- Comment #4 from Yuri Pankov  ---
(In reply to Yasuhiro KIMURA from comment #3)
As a matter of fact, yes:

* '(foo|)':
--
|
The vertical-line is special except when used in a bracket expression. A
vertical-line appearing first or last in an ERE, or immediately following a
vertical-line or a left-parenthesis, or immediately preceding a
right-parenthesis, produces undefined results.
--

* '.{0,256}':
We have RE_DUP_MAX defined to 255 (see /usr/include/limits.h).


For reference:
https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap09.html

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 188213] gpart(8): gpart device designator handling is inconsistant

[bugzilla-noreply]

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

--- Comment #2 from commit-h...@freebsd.org ---
A commit references this bug:

Author: rew
Date: Sat Dec 12 07:22:38 UTC 2020
New revision: 368576
URL: https://svnweb.freebsd.org/changeset/base/368576

Log:
  geom(8): list geoms with /dev/ prefix

  Allow geom(8) to list geoms with the '/dev/' prefix.

  `geom part show` accepts the '/dev/' prefix but `geom part list` does not.

  Modify find_geom() in sbin/geom/core/geom.c to be consistent with the
behavior
  of find_geom() in lib/geom/part/geom_part.c.

  PR: 188213
  Reported by:Ronald F. Guilmette 
  Reviewed by:imp, kevans
  Approved by:kevans (mentor)
  MFC after:  1 week
  Differential Revision:  https://reviews.freebsd.org/D27556

Changes:
  head/sbin/geom/core/geom.c

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 251775] bsdgrep: egrep regards '{foo}' as invalid regular expression

[bugzilla-noreply]

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

--- Comment #5 from Yasuhiro KIMURA  ---
(In reply to Yuri Pankov from comment #4)

I see. Thank you for answering my question.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

[Bug 188213] gpart(8): gpart device designator handling is inconsistant

[bugzilla-noreply]

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

Robert Wing  changed:

   What|Removed |Added

 Status|Open|Closed
 CC||r...@freebsd.org
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"