nawawi
Repos
125
Followers
47
Following
48

A persistent object cache stored as a plain PHP code, accelerates caching with OPcache backend.

18
5

Docket CronWP is a command-line tool for executing WordPress cron events in parallel.

9
3

eyeOS v2.5 -- the last release under an open source license

7
15

This is a Github mirror for Xtables-addons, a set of additional extensions for the Xtables packet filter that is present in the Linux kernel

C
2
0

This is a Github mirror for Buildroot, a simple, efficient and easy-to-use tool to generate embedded Linux systems through cross-compilation.

0
1

This is a Github mirror for Klish, a framework for implementing a CISCO-like CLI on a UNIX systems. https://src.libcode.org/pkun/klish.git

C
13
11

Events

Created at 6 days ago
started
Created at 6 days ago
Created at 1 week ago
Created at 1 week ago
Created at 1 month ago
closed issue
wp_cache_flush_group

Hello there. Thank you for this project! FYI, a function named wp_cache_flush_group was introduced in the development version of WordPress. You might want to check it.

Created at 1 month ago
issue comment
wp_cache_flush_group

Hi, thanks for the info. Btw, we already implemented it, you may refer to https://github.com/nawawi/docket-cache/blob/master/includes/cache.php#L2130

Thanks.

Created at 1 month ago
Created at 2 months ago

Fix makedebian.pl

Fix makerpm.pl

Fix setup.sh

Fix setup.sh

Update zh

Iam sorry that some of them are confusing in Webmin

Correct confusing translations

I apologize for confusing translations

Update zh

Update module.info.zh

Update module.info.zh

Delete module.info.zh.auto

Update zh.auto

Rename zh.auto to zh

localized translation

Add entry to zh-cn version readme

Merge pull request #1678 from unknown10777/master

Adds few zh-cn translations and a zh-cn version of readme.

Update README.md contributors

Revert "Update README.md contributors"

This reverts commit d3691a433fa2d4a05faadfebda00a45173124efa.

Update README.md contributors

Update link to a new README-zh-cn.md file

Add fallback in case PATH is somehow not set

Created at 2 months ago

Snap: support arm64

Explicitly mark arm64 as supported build platform. Curiously, this doesn't seem to be needed to build on arm64...

Snap: improve startup times by using LZO

Opt-in to LZO compression so that first launch of Poedit snap is faster.

See https://ubuntu.com/blog/snap-speed-improvements-with-new-compression-algorithm

Snap: add title

Snap: fix broken fonts on Ubuntu 22.04

The snap accidentally included second copy of GTK+ runtime which didn't behave correctly. Fix by purging this copy and using only gnome-platform as it was supposed to be doing.

See the same issue and fix in LibreOffice: https://github.com/ubuntu/libreoffice/issues/11 https://github.com/ubuntu/libreoffice/pull/12/files

In Poedit's case, we need to take care to not remove libgtkspell, which is used, and installing which probably pulled in the libraries in the first place.

Crowdin: sort projects and languages in UI

Sort the list of projects as well as languages alphabetically in Crowdin picker UI, instead of keeping the (somewhat arbitrary) server-returned order.

Merge branch 'devel/linux-packaging-fixes'

Update translations from Crowdin

Change version to 3.1.1 and update NEWS

Migrate Travis CI job to Github Actions

Note that publishing the release is not supported yet.

Cancel in-progress CI jobs on subsequent push

Add CI build for macOS

Use ccache for Linux and macOS CI builds

Add Windows CI build

Produce source tarball as artifact from CI build

Make macOS build of gettext slightly faster

Use Autoconf caching to speed up sub-configure runs when building gettext. This saves approx. 1 minute per arch.

Use 8.3 filenames in FixDuplicateItems() too

Harden gettext invocation in POCatalog::FixDuplicateItems() against codepage, whitespace etc. issues using CliSafeFileName() as is done in other places.

Fixes #763.

Automatically prepare GitHub releases on tag push

apt-get update needs to be run before install

Without this, install may fail because the .deb files referenced by the index may already be out of date and missing from Ubuntu mirrors.

Merge branch 'devel/github-actions'

Merge remote-tracking branch 'upstream/master' into stable

Created at 2 months ago

Automatic text/csv detection

Merge pull request #2727 from Cleptomania/csv

Automatic text/csv detection

Changelog

Update PHPMailer.php

Cleanup

Merge pull request #2728 from evan70/master

trim(): Passing null to parameter ($string) of type string is deprecated

Use higher debug level when demonstrating TLS options

Clarify SMTP auth options, fixes #2732

GH Actions: Bump JamesIves/github-pages-deploy-action

Bumps JamesIves/github-pages-deploy-action from 4.3.4 to 4.4.0.


updated-dependencies:

  • dependency-name: JamesIves/github-pages-deploy-action dependency-type: direct:production update-type: version-update:semver-minor ...

Signed-off-by: dependabot[bot] support@github.com

Merge pull request #2735 from PHPMailer/dependabot/github_actions/JamesIves/github-pages-deploy-action-4.4.0

GH Actions: Bump JamesIves/github-pages-deploy-action from 4.3.4 to 4.4.0

Merge remote-tracking branch 'upstream/master'

Created at 2 months ago

hello world

Created at 2 months ago

[FIX] web: session cookie lost between requests

Each cookie binds to a domain name, multiple cookies can be set for the same name if they are for different domain name. In this case, two session_id cookies were set: (1) the first set right on the opener at opener.cookies[...] = ..., (2) the second set upon inside of http.Request._save_session because the session was rotated upon login. The problem is that the former cookie (the one set on the opener, the one not rotated) was used instead of the second cookie (the one holding the registered user) in the subsequent queries. There is a long comment explaining the same problem inside of odoo.tests.common.HttpCase.authenticate, we used the same solution as they did inside of authenticate: we diched the previous opener.

closes odoo/odoo#94773

Signed-off-by: Christophe Monniez (moc) moc@odoo.com

[FIX] web_editor: restore media dialog cleanup of each media type

Since 1 when the media dialog was refactored to owl, some of the classes clean up when switching across media types were lost.

This commit restores the clean up for each media type - as they were before 1.

Steps to reproduce: (Just one example - there are many scenarios)

  • Drop a "Text - Image" block.
  • Apply a rounded circle on the image.
  • Replace the image by a video. => The rounded circle effect remains but cannot be removed.

task-2829971

Part-of: odoo/odoo#95287

[FIX] web_editor: align icon to the right

When replacing an image by a pictogram, the classes of the previous media are copied to the new icon's <span>. This potentially includes the w-100 class which prevents the alignment from behaving correctly.

This commit removes the w-100 class if it exists.

Steps to reproduce:

  • Drop a "Media List" block
  • Replace first image by pictogram.
  • Align icon to the right. => Icon was displayed aligned to the left.

task-2829971 (was task-2729177)

closes odoo/odoo#95287

X-original-commit: https://github.com/odoo/odoo/commit/8f71a3c55dcaae738fbb673266aa400b4c4a1fa4 Signed-off-by: Quentin Smetz (qsm) qsm@odoo.com

[FIX] payment: cron miss online payments of long verification

Sometime Paypal took 3 or 4 days for some payment verification due to weekend. This raises the retry limit days for 4 days instead of 2 to solve the issue

closes odoo/odoo#95522

X-original-commit: 5aaaaf8f072b3f8ab66a269bb3dba02714b593ad Signed-off-by: Antoine Vandevenne (anv) anv@odoo.com

[IMP] repair: convert repair uom and location onchanges to compute

This allows to create a repair.order record without the need to call the onchanges to set the uom and locations or to set them manually during the create call.

For instance, this makes easier to create repair orders using XMLRPC when you do not use multiple UOMs or multiple locations.

closes odoo/odoo#95321

Signed-off-by: Raphael Collet rco@odoo.com

[FIX] point_of_sale: no pos -> hide config options

We hide all pos-related config options when no pos is selected to unblock users from saving the general settings.

closes odoo/odoo#95464

Signed-off-by: Masereel Pierre pim@odoo.com

[FW][MOV] knowledge: extract method to detach children

This commit extracts the logic in "action_archive" that detaches children articles to which the current user does not have access to into a separate method. See 'KnowledgeArticle._detach_unwritable_descendants()' for details.

This is a preliminary work to introduce the next fixes that will apply that logic when making an article private as well. There should be no functional change with this commit.

Task-2859616

X-original-commit: odoo/odoo@94ed05d6e88b6695ef5adc4b8113b96adf7d06c1 Part-of: odoo/odoo#95471

[FW][MOV] knowledge: extract method to make private

This commit extracts logic necessary to make an article private from move_to into its own method. This helps understanding what is done and allow to be called in other flows. Indeed moving under another parent and making private are actually quite different flows.

This is a preliminary work to introduce the next fixes that will add changes necessary to correctly handle private articles update.

Task-2859616

X-original-commit: odoo/odoo@6a3f07e38465c4b237738520b613e8c05399104f Part-of: odoo/odoo#95471

[FW][REF] (website_)knowledge: lint and cleanup tests

This commit contains some post-merge cleanup in knowledge tests before adding some new tests

  • remove an unused common file, holding unused data;
  • some rephrasing and cleanup in comments;
  • move fields specific test into an "internal" file that holds tests for computed fields notably;

Task-2859616

X-original-commit: odoo/odoo@bad3ee069e8860d4259160e1222fd6a9fdaef562 Part-of: odoo/odoo#95471

[FW][IMP] knowledge: improve a bit common data / classes

Purpose: remove custom data in tests when possible, try to re-use existing data. Improve default data to cover most use cases without being too much complex to handle.

Add information to clearly explain hierarchy and better understand tests impact, in common classes or specific tests generating their own test structure.

Check tests effectively test what they intend to.

Task-2859616

X-original-commit: odoo/odoo@de92822ac4ba8d1302326ed82e8ef45e643ccd4d Part-of: odoo/odoo#95471

[FW][FIX] knowledge: fix ordering, especially with user preferences

Several issues with article model ordering have been found and are fixed in this commit:

  • default order of model as favorite_count currently ascending while we actually want most favorite articles to be on top;
  • when searching sorted articles per user, we use the sequence on favorite model. When ordering on this field we therefore have to fetch all favorite articles and then order them based on user's sequence. Otherwise when having more favorite articles than asked the user's sequence is not taken into account;
  • specify order in various searches to make it explicit;

Task-2901990

X-original-commit: odoo/odoo@bbabb2fdb6ab8b0f6c5529ec27efb2b5ccfc3a86 Part-of: odoo/odoo#95471

[FW][PRF] knowledge: use _search for 2many-based favorite field

Improve performance of search on favorite articles by using _search. This allows to have less specific queries and use ORM capabilities.

Task-2901990

X-original-commit: odoo/odoo@ed72a92be36f99a746456b6cda0286e266dda3dd Part-of: odoo/odoo#95471 Co-authored-by: Aurélien Warnon awa@odoo.com

[FW][FIX] knowledge: correctly set rule permission

Correctly set write access rule to write (and create) instead of being global. Read rule for internals and portal users is based on has_access field. Also add some additional details in rules name to make their name explicit and understand the rule purpose at a glance.

Task-2859616

X-original-commit: odoo/odoo@ba05b7a87c3aea7da75cbd003fba8b7a1905dbb3 Part-of: odoo/odoo#95471

[FW][FIX] knowledge: do not crash when public reads is_user_favorite

Reading is_user_favorite requires access on intermediate favorite model. It is however not accessible to public users. Reading the field therefore raises an error which is not necessary.

We can simply set the field to False as public users can not set articles as favorite and skip the whole computation.

Task-2859616

X-original-commit: odoo/odoo@fe854b3636a720282e028f1c74203af15a7acdbe Part-of: odoo/odoo#95471

[FW][FIX][IMP] knowledge: lessen usage of member writable constraint

Purpose of this commit is to have less check on "is writable" constraint from member model. With a new context key we can now bypass the constraint from member model when we are sure it is globally verified. As in some cases we modify members from an article, the constraint will be checked at article level with all members being updated. In some cases doing specific checks might lead to issues when the constraint is evaluated in a transient state e.g. when a member is removed while new write members are not yet added.

Task-2859616

X-original-commit: odoo/odoo@a4aa8569026b02f57d86dafcb5c2c140526f38ac Part-of: odoo/odoo#95471 Co-authored-by: Aurélien Warnon awa@odoo.com Co-authored-by: Thibault Delavallee tde@odoo.com

[FW][FIX] knowledge: correctly handle writer check when removing memberships

This commit fixes the check that verifies that the article always has a member with write access on the article.

Indeed, the current code was using a database request to check for members with write access in a "api.constrains" check, where the data being updated is not flushed into database yet.

It now correctly uses fields access directly, as stated by the method docstring. For convenience, we extracted the "_has_writer_member" method to be re-usable.

An additional test case has been added to enforce the behavior.

Task-2859616

X-original-commit: odoo/odoo@ccdfb791f87fbad39c45abcaada36d23f73a8f05 Part-of: odoo/odoo#95471

[FW][FIX] knowledge: correctly copy members when desynchronizing on archive

Currently, when archiving an article, if you don't have write access to some of the children of the article, we do not archive them and do some extra post-processing.

Meaning:

  • They become independent from the archived parent
  • They are moved as "root articles"
  • The potential specific member access from their parent(s) are copied To avoid loosing access if specific members where configured on the parent(s) of those articles, since they will no-longer inherit from them.

This last part was not working properly and has been fixed. Existing tests have been adapted to ensure the behavior is kept.

Task-2859616

X-original-commit: odoo/odoo@b35f2ace22899f00c090801e476889b8d5cdbe03 Part-of: odoo/odoo#95471

[FW][FIX] knowledge: correctly propagate to children when moving to private

Currently, when moving an article to the private section, its children are untouched and keep their access rights.

This is incorrect: when making an article private, all (accessible) children should be made private as well.

See 'knowledge.article#_make_private' for details.

An exception is made for children articles to which the user does not have a write access to.

Those are handled as the following (same as archiving flow):

  • They become independent from the parent
  • They are moved as "root articles"
  • The potential specific member access from their parent(s) are copied To avoid loosing access if specific members where configured on the parent(s) of those articles, since they will no-longer inherit from them.

Tests were added to enforce this behavior.

Task-2859616

X-original-commit: odoo/odoo@82af404c5b281efae090c7c181e460b98e2575f1 Part-of: odoo/odoo#95471

[FW][FIX] knowledge: correctly handle desync status when detaching children

This commit fixes the case when we have desynchronized children for which the current user does not have write access and we move the parent to the private section (or archive the parent).

In that case, children that are desynchronized should not have the members from their parents copied onto them when detaching.

See '_detach_unwritable_descendants' and associated tests for more details.

Task-2859616

X-original-commit: odoo/odoo@348740fa9fe52f69914c446490fa5f37cb84090b Part-of: odoo/odoo#95471

[FW][FIX] knowledge: correctly handle complete hierarchy when detaching children

Currently, when archiving or moving an article to private, we "detach" children of that article to which the current user does not have (write) access to. This essentially means that these unreachable articles are detached from their parent and set as root articles. See ``_detach_unwritable_descendants' for more details.

However, during that process, we incorrectly considered only the direct children of the archived / moved article.

This commit fixes it by taking into account the whole hierarchy that is going to be modified, as archiving and making private actually propagates to all the (reachable) article children.

Task-2859616

X-original-commit: odoo/odoo@a31f48dfa4a6940356d44796b1e35fc5a6cebac5 Part-of: odoo/odoo#95471

Created at 2 months ago

Fix the Popup-trigger for FileAttachmentAnnotationElement (PR 15036 follow-up)

After the changes in PR 15036, the trigger-element created in FileAttachmentAnnotationElement.render is now too small. This can be fixed by using the same approach as in PR 15065, and the patch can be tested using the annotation-fileattachment.pdf document in the test-suite.

[Editor] Update the id for a l10n string

Merge pull request #15126 from calixteman/update_l10n_id

[Editor] Update the id for a l10n string

Merge pull request #15125 from Snuffleupagus/FileAttachmentAnnotationElement-trigger

Fix the Popup-trigger for FileAttachmentAnnotationElement (PR 15036 follow-up)

Call AnnotationLayer.setDimensions as part of the render/update-methods (PR 15036 follow-up)

Rather than forcing the user to manually call setDimensions, which is also breaking any existing third-party code, it seems that we can simply let the AnnotationLayer.{render, update}-methods handle that internally.

As far as I can tell, based on testing manually in the viewer and running the browser-tests, everything still appears to work correctly with this patch.

Merge pull request #15124 from Snuffleupagus/private-setDimensions

Call AnnotationLayer.setDimensions as part of the render/update-methods (PR 15036 follow-up)

Improve text-selection for Type3 fonts with bogus /FontBBox-entries (issue 14999)

This extends PR 13461, by also building a fallback bounding box for Type3 fonts that contain a much too small /FontBBox-entry.

Please note: While this patch improves things overall, copy-and-pasting still doesn't work perfectly for this document. In particular the lowercase letter "c" cannot be selected/copied, however this can be reproduced in both Adobe Reader and PDFium (in Google Chrome) too, which is caused by a lack of proper /ToUnicode-data in the PDF document.

Merge pull request #15133 from Snuffleupagus/issue-14999

Improve text-selection for Type3 fonts with bogus /FontBBox-entries (issue 14999)

[Editor] Dispatch an event when some global states are changing

  • this way the context menu in Firefox can take into account what we have in the clipboard, if an editor is selected, ...
  • when the user will click on a context menu item, an action will be triggered, hence this patch adds what is required to handle it;
  • some tests will be added in the Firefox' patch.

Merge pull request #15130 from calixteman/context_menu

[Editor] Dispatch an event when some global states are changing (bug 1777695)

[editor] Use the fit-curve package (issue 15004)

Rather than including all of this external code in the PDF.js repository, we should be using the npm package instead. Unfortunately this is slightly more complicated than you'd hope, since the fit-curve package (which is older) isn't directly compatible with modern JavaScript modules. In particular, the following cases needed to be considered:

  • For the development viewer (i.e. gulp server) and the unit-tests, we thus need to build a fitCurve-bundle that can be directly imported.
  • For the actual PDF.js build-targets, we can slightly reduce the sizes by depending on the "raw" fit-curve source-code.
  • For the Node.js unit-tests, the fit-curve package can be used as-is.

Merge pull request #15142 from Snuffleupagus/fitCurve

[editor] Use the fit-curve package (issue 15004)

[Editor] Allow editors deletion on Backspace or Delete keys

Merge pull request #15144 from calixteman/editing_delete

[Editor] Allow editors deletion on Backspace or Delete keys

[api-minor] Deprecate the enhanceTextSelection functionality

[jsdoc] failing typescript builds - wrong type

HTMLSectionElement is not part of the DOM, so the generated typescript definitions contain a non-existing type.

HTML Section elements have to be handled as simple HTMLElements.

fixing punctuation and lint problems

[jsdoc] failing typescript builds - wrong type

[Editor] Change the cursor to a pen for the Ink editor

[Editor] Avoid to resize and redraw the ink canvas when it's useless

  • and because of rounding errors it led to slightly resize again and again the ink container;
  • when zooming the size is changing but not the ratio, so in this case we don't need to change the dimension of the container.

Merge pull request #15146 from calixteman/editing_cursor

[Editor] Change the cursor to a pen for the Ink editor

Merge pull request #15143 from bernatgy/typescript-compilation-fix

[jsdoc] failing typescript builds - wrong type

Created at 2 months ago

xfrm: xfrm_policy: fix a possible double xfrm_pols_put() in xfrm_bundle_lookup()

xfrm_policy_lookup() will call xfrm_pol_hold_rcu() to get a refcount of pols[0]. This refcount can be dropped in xfrm_expand_policies() when xfrm_expand_policies() return error. pols[0]'s refcount is balanced in here. But xfrm_bundle_lookup() will also call xfrm_pols_put() with num_pols == 1 to drop this refcount when xfrm_expand_policies() return error.

This patch also fix an illegal address access. pols[0] will save a error point when xfrm_policy_lookup fails. This lead to xfrm_pols_put to resolve an illegal address in xfrm_bundle_lookup's error path.

Fix these by setting num_pols = 0 in xfrm_expand_policies()'s error path.

Fixes: 80c802f3073e ("xfrm: cache bundles instead of policies for outgoing flows") Signed-off-by: Hangyu Hua hbh25y@gmail.com Signed-off-by: Steffen Klassert steffen.klassert@secunet.com

arm64: dts: rockchip: Fix ethernet on production Quartz64-B

The production Quartz64 Model B has compatibility issues when using rgmii-id mode. Switch to rgmii mode and use the SoC's delays to ensure full compatibility.

Reported-by: Frank Mankel frank.mankel@gmail.com Fixes: dcc8c66bef79 ("arm64: dts: rockchip: add Pine64 Quartz64-B device tree") Signed-off-by: Peter Geis pgwipeout@gmail.com Tested-by: Frank Mankel frank.mankel@gmail.com Link: https://lore.kernel.org/r/20220606163023.3677147-1-pgwipeout@gmail.com Signed-off-by: Heiko Stuebner heiko@sntech.de

power: supply: ab8500_fg: add missing destroy_workqueue in ab8500_fg_probe

In ab8500_fg_probe, misses destroy_workqueue in error path, this patch fixes that.

Fixes: 010ddb813f35 ("power: supply: ab8500_fg: Allocate wq in probe") Signed-off-by: Gao Chao gaochao49@huawei.com Reviewed-by: Linus Walleij linus.walleij@linaro.org Signed-off-by: Sebastian Reichel sebastian.reichel@collabora.com

power/reset: arm-versatile: Fix refcount leak in versatile_reboot_probe

of_find_matching_node_and_match() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. Add missing of_node_put() to avoid refcount leak.

Fixes: 0e545f57b708 ("power: reset: driver for the Versatile syscon reboot") Signed-off-by: Miaoqian Lin linmq006@gmail.com Reviewed-by: Linus Walleij linus.walleij@linaro.org Signed-off-by: Sebastian Reichel sebastian.reichel@collabora.com

power: supply: core: Fix boundary conditions in interpolation

The functions power_supply_temp2resist_simple and power_supply_ocv2cap_simple handle boundary conditions incorrectly. The change was introduced in a4585ba2050f460f749bbaf2b67bd56c41e30283 ("power: supply: core: Use library interpolation"). There are two issues: First, the lines "high = i - 1" and "high = i" in ocv2cap have the wrong order compared to temp2resist. As a consequence, ocv2cap sets high=-1 if ocv>table[0].ocv, which causes an out-of-bounds read. Second, the logic of temp2resist is also not correct. Consider the case table[] = {{20, 100}, {10, 80}, {0, 60}}. For temp=5, we expect a resistance of 70% by interpolation. However, temp2resist sets high=low=2 and returns 60.

Cc: stable@vger.kernel.org Signed-off-by: Dorian Rudolph mail@dorianrudolph.com Reviewed-by: Linus Walleij linus.walleij@linaro.org Fixes: a4585ba2050f ("power: supply: core: Use library interpolation") Signed-off-by: Sebastian Reichel sebastian.reichel@collabora.com

rtw88: 8821c: fix access const table of channel parameters

We would like to make chip_info table const, but 8821c uses one field as a variable, and causes core dump. To fix this, move the field to another struct that can be read and written.

BUG: unable to handle page fault for address: ffffffffc09f52f4 PGD 5b5215067 P4D 5b5215067 PUD 5b5217067 PMD 111f61067 PTE 8000000111e07161 Oops: 0003 [#1] PREEMPT SMP NOPTI CPU: 6 PID: 436 Comm: NetworkManager Not tainted 5.18.0-rc7-debug-01822-g89d8f53ff6e7 #1 5cac31ca93432e53341863abfb3332fd98b144da Hardware name: HP HP Desktop M01-F1xxx/87D6, BIOS F.12 12/17/2020 RIP: 0010:rtw8821c_phy_set_param+0x262/0x380 [rtw88_8821c] Code: e8 53 f3 c0 d6 48 8b 43 10 4c 8b 63 38 be 24 0a 00 00 48 89 df 48 8b 40 68 e8 3a f3 c0 d6 89 e9 be 28 0a 00 00 48 89 df d3 e8 <41> 89 84 24 54 01 00 00 48 8b 43 10 4c 8b 63 38 48 8b 40 68 e8 15 RSP: 0018:ffffb08c417cb6f0 EFLAGS: 00010286 RAX: 0000000064b80c1c RBX: ffff93d15a0120e0 RCX: 0000000000000000 RDX: 0000000034028211 RSI: 0000000000000a28 RDI: ffff93d15a0120e0 RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000001 R11: 0000000000000006 R12: ffffffffc09f51a0 R13: ffff93d15a0156d0 R14: 0000000000000000 R15: 0000000000000001 FS: 00007f4e9b73d1c0(0000) GS:ffff93d83ab80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffffffc09f52f4 CR3: 0000000103b9e000 CR4: 0000000000350ee0 Call Trace: rtw_core_start+0xbd/0x190 [rtw88_core de79d6bdfd083d102030858972032e5706726279] rtw_ops_start+0x26/0x40 [rtw88_core de79d6bdfd083d102030858972032e5706726279] drv_start+0x42/0x100 [mac80211 21e803d0ad10691f64c6c81ecc24c0c6c36e5d58] ieee80211_do_open+0x2fb/0x900 [mac80211 21e803d0ad10691f64c6c81ecc24c0c6c36e5d58] ieee80211_open+0x67/0x80 [mac80211 21e803d0ad10691f64c6c81ecc24c0c6c36e5d58] __dev_open+0xdd/0x180 [...]

Fixes: 89d8f53ff6e7 ("wifi: rtw88: Fix Sparse warning for rtw8821c_hw_spec") Reported-by: Nathan Chancellor nathan@kernel.org Cc: Larry Finger Larry.Finger@lwfinger.net Signed-off-by: Ping-Ke Shih pkshih@realtek.com Tested-by: Nathan Chancellor nathan@kernel.org Signed-off-by: Kalle Valo kvalo@kernel.org Link: https://lore.kernel.org/r/20220608020312.9663-1-pkshih@realtek.com

arm64: dts: rockchip: Fix Quartz64-A dwc3 otg port behavior

The otg_id line on the Quartz64 Model A is not connected to anything. This prevents automatic selection of the dual role usb port. In otg mode it defaults to device mode. Force it to host mode to retain previous behavior.

Fixes: bc405bb3eeee ("arm64: dts: rockchip: enable otg/drd operation of usb_host0_xhci in rk356x") Signed-off-by: Peter Geis pgwipeout@gmail.com Link: https://lore.kernel.org/r/20220610132542.159978-1-pgwipeout@gmail.com Signed-off-by: Heiko Stuebner heiko@sntech.de

arm64: dts: rockchip: Assign RK3399 VDU clock rate

Before commit 9998943f6dfc ("media: rkvdec: Stop overclocking the decoder"), the rkvdec driver was forcing the VDU clock rate. After that commit, we rely on the default clock rate. That rate works OK on many boards, with the default PLL settings (CPLL is 800MHz, VDU dividers leave it at 400MHz); but some boards change PLL settings.

Assign the expected default clock rate explicitly, so that the rate is consistent, regardless of PLL configuration.

This was particularly broken on RK3399 Gru Scarlet systems, where the rk3399-gru-scarlet.dtsi assigns PLL_CPLL to 1.6 GHz, and so the VDU clock ends up at 800 MHz (twice the expected rate), and causes video artifacts and other issues.

Note: I assign the clock rate in the clock controller instead of the vdec node, because there are multiple nodes that use this clock, and per the clock.yaml specification:

Configuring a clock's parent and rate through the device node that consumes the clock can be done only for clocks that have a single user. Specifying conflicting parent or rate configuration in multiple consumer nodes for a shared clock is forbidden.

Configuration of common clocks, which affect multiple consumer devices can be similarly specified in the clock provider node.

Fixes: 9998943f6dfc ("media: rkvdec: Stop overclocking the decoder") Cc: stable@vger.kernel.org Signed-off-by: Brian Norris briannorris@chromium.org Reviewed-by: Nicolas Dufresne nicolas.dufresne@collabora.com Link: https://lore.kernel.org/r/20220607141535.1.Idafe043ffc94756a69426ec68872db0645c5d6e2@changeid Signed-off-by: Heiko Stuebner heiko@sntech.de

dt-bindings: net: wireless: ath9k: Change Toke as maintainer

Toke now maintains ath9k so update DT bindings as well.

Signed-off-by: Kalle Valo quic_kvalo@quicinc.com Acked-by: Toke Høiland-Jørgensen toke@toke.dk Signed-off-by: Kalle Valo kvalo@kernel.org Link: https://lore.kernel.org/r/20220610133640.10810-1-kvalo@kernel.org

dt-bindings: net: wireless: ath11k: change Kalle's email

My codeaurora.org email doesn't work anymore, so switch to my preferred kernel.org address.

Signed-off-by: Kalle Valo quic_kvalo@quicinc.com Signed-off-by: Kalle Valo kvalo@kernel.org Link: https://lore.kernel.org/r/20220610133640.10810-2-kvalo@kernel.org

Revert "evm: Fix memleak in init_desc"

This reverts commit ccf11dbaa07b328fa469415c362d33459c140a37.

Commit ccf11dbaa07b ("evm: Fix memleak in init_desc") said there is memleak in init_desc. That may be incorrect, as we can see, tmp_tfm is saved in one of the two global variables hmac_tfm or evm_tfm[hash_algo], then if init_desc is called next time, there is no need to alloc tfm again, so in the error path of kmalloc desc or crypto_shash_init(desc), It is not a problem without freeing tmp_tfm.

And also that commit did not reset the global variable to NULL after freeing tmp_tfm and this makes *tfm a dangling pointer which may cause a UAF issue.

Reported-by: Guozihua (Scott) guozihua@huawei.com Signed-off-by: Xiu Jianfeng xiujianfeng@huawei.com Signed-off-by: Mimi Zohar zohar@linux.ibm.com

cgroup: Use separate src/dst nodes when preloading css_sets for migration

Each cset (css_set) is pinned by its tasks. When we're moving tasks around across csets for a migration, we need to hold the source and destination csets to ensure that they don't go away while we're moving tasks about. This is done by linking cset->mg_preload_node on either the mgctx->preloaded_src_csets or mgctx->preloaded_dst_csets list. Using the same cset->mg_preload_node for both the src and dst lists was deemed okay as a cset can't be both the source and destination at the same time.

Unfortunately, this overloading becomes problematic when multiple tasks are involved in a migration and some of them are identity noop migrations while others are actually moving across cgroups. For example, this can happen with the following sequence on cgroup1:

#1> mkdir -p /sys/fs/cgroup/misc/a/b #2> echo $$ > /sys/fs/cgroup/misc/a/cgroup.procs #3> RUN_A_COMMAND_WHICH_CREATES_MULTIPLE_THREADS & #4> PID=$! #5> echo $PID > /sys/fs/cgroup/misc/a/b/tasks #6> echo $PID > /sys/fs/cgroup/misc/a/cgroup.procs

the process including the group leader back into a. In this final migration, non-leader threads would be doing identity migration while the group leader is doing an actual one.

After #3, let's say the whole process was in cset A, and that after #4, the leader moves to cset B. Then, during #6, the following happens:

  1. cgroup_migrate_add_src() is called on B for the leader.

  2. cgroup_migrate_add_src() is called on A for the other threads.

  3. cgroup_migrate_prepare_dst() is called. It scans the src list.

  4. It notices that B wants to migrate to A, so it tries to A to the dst list but realizes that its ->mg_preload_node is already busy.

  5. and then it notices A wants to migrate to A as it's an identity migration, it culls it by list_del_init()'ing its ->mg_preload_node and putting references accordingly.

  6. The rest of migration takes place with B on the src list but nothing on the dst list.

This means that A isn't held while migration is in progress. If all tasks leave A before the migration finishes and the incoming task pins it, the cset will be destroyed leading to use-after-free.

This is caused by overloading cset->mg_preload_node for both src and dst preload lists. We wanted to exclude the cset from the src list but ended up inadvertently excluding it from the dst list too.

This patch fixes the issue by separating out cset->mg_preload_node into ->mg_src_preload_node and ->mg_dst_preload_node, so that the src and dst preloadings don't interfere with each other.

Signed-off-by: Tejun Heo tj@kernel.org Reported-by: Mukesh Ojha quic_mojha@quicinc.com Reported-by: shisiyuan shisiyuan19870131@gmail.com Link: http://lkml.kernel.org/r/1654187688-27411-1-git-send-email-shisiyuan@xiaomi.com Link: https://www.spinics.net/lists/cgroups/msg33313.html Fixes: f817de98513d ("cgroup: prepare migration path for unified hierarchy") Cc: stable@vger.kernel.org # v3.16+

gpiolib: cdev: Fix kernel doc for struct line

Kernel doc validator is not happy: gpiolib-cdev.c:487: warning: Function parameter or member 'hdesc' not described in 'line' gpiolib-cdev.c:487: warning: Function parameter or member 'raw_level' not described in 'line' gpiolib-cdev.c:487: warning: Function parameter or member 'total_discard_seq' not described in 'line' gpiolib-cdev.c:487: warning: Function parameter or member 'last_seqno' not described in 'line'

Describe above mentioned parameters.

Fixes: 2068339a6c35 ("gpiolib: cdev: Add hardware timestamp clock type") Signed-off-by: Andy Shevchenko andriy.shevchenko@linux.intel.com Acked-by: Dipen Patel dipenp@nvidia.com Acked-by: Bartosz Golaszewski brgl@bgdev.pl Signed-off-by: Thierry Reding treding@nvidia.com

ARM: rockchip: Add missing of_node_put() in rockchip_suspend_init()

In rockchip_suspend_init(), of_find_matching_node_and_match() will return a node pointer with refcount incremented. We should use of_node_put() in fail path or when it is not used anymore.

Signed-off-by: Liang He windhl@126.com Link: https://lore.kernel.org/r/20220616021713.3973472-1-windhl@126.com Signed-off-by: Heiko Stuebner heiko@sntech.de

serial: 8250: dw: enable using pdata with ACPI

Commit ffd381445eac ("serial: 8250: dw: Move the USR register to pdata") caused NULL-pointer dereference when booting with ACPI by unconditional usage of the recently added pdata.

In order to fix that and prevent similar issues in future, hook the default version of this structure in dw8250_acpi_match table. While at it, sort all entries alphabetically.

Fixes: ffd381445eac ("serial: 8250: dw: Move the USR register to pdata") Reviewed-by: Ilpo Järvinen ilpo.jarvinen@linux.intel.com Reviewed-by: Andy Shevchenko andy.shevchenko@gmail.com Signed-off-by: Marcin Wojtas mw@semihalf.com Link: https://lore.kernel.org/r/20220620121046.1307412-1-mw@semihalf.com Signed-off-by: Greg Kroah-Hartman gregkh@linuxfoundation.org

tty: serial: samsung_tty: set dma burst_size to 1

The src_maxburst and dst_maxburst have been changed to 1 but the settings of the UCON register aren't changed yet. They should be changed as well according to the dmaengine slave config.

Fixes: aa2f80e752c7 ("serial: samsung: fix maxburst parameter for DMA transactions") Cc: stable stable@kernel.org Cc: Marek Szyprowski m.szyprowski@samsung.com Reviewed-by: Krzysztof Kozlowski krzysztof.kozlowski@linaro.org Signed-off-by: Chanho Park chanho61.park@samsung.com Link: https://lore.kernel.org/r/20220627065113.139520-1-chanho61.park@samsung.com Signed-off-by: Greg Kroah-Hartman gregkh@linuxfoundation.org

serial: pl011: UPSTAT_AUTORTS requires .throttle/unthrottle

The driver must provide throttle and unthrottle in uart_ops when it sets UPSTAT_AUTORTS. Add them using existing stop_rx & enable_interrupts functions.

Fixes: 2a76fa283098 (serial: pl011: Adopt generic flag to store auto RTS status) Cc: stable stable@kernel.org Cc: Lukas Wunner lukas@wunner.de Reported-by: Nuno Gonçalves nunojpg@gmail.com Tested-by: Nuno Gonçalves nunojpg@gmail.com Signed-off-by: Ilpo Järvinen ilpo.jarvinen@linux.intel.com Link: https://lore.kernel.org/r/20220614075637.8558-1-ilpo.jarvinen@linux.intel.com Signed-off-by: Greg Kroah-Hartman gregkh@linuxfoundation.org

serial: 8250: Fix __stop_tx() & DMA Tx restart races

Commit e8ffbb71f783 ("serial: 8250: use THRE & __stop_tx also with DMA") changed __dma_tx_complete() to enable THRI that is cleared in __stop_tx() once THRE is asserted as UART runs out bits to transmit. It is possible, however, that more data arrives in between in which case serial8250_tx_dma() resumes Tx. THRI is not supposed to be on during DMA Tx because DMA is based on completion handler, therefore THRI must be cleared unconditionally in serial8250_tx_dma().

When Tx is about to start, another race window exists with serial8250_handle_irq() leading to a call into __stop_tx() while the Tx has already been resumed:

__tx_complete(): -> spin_lock(port->lock) -> dma->tx_running = 0 -> serial8250_set_THRI() -> spin_unlock(port->lock)

uart_start(): serial8250_handle_irq(): -> spin_lock(port->lock) -> serial8250_tx_dma(): -> dma->tx_running = 1 -> spin_unlock(port->lock) -> spin_lock(port->lock) -> __stop_tx()

Close this race by checking !dma->tx_running before calling into __stop_tx().

Fixes: e8ffbb71f783 ("serial: 8250: use THRE & __stop_tx also with DMA") Signed-off-by: Ilpo Järvinen ilpo.jarvinen@linux.intel.com Link: https://lore.kernel.org/r/20220615090651.15340-2-ilpo.jarvinen@linux.intel.com Signed-off-by: Greg Kroah-Hartman gregkh@linuxfoundation.org

tty: Add N_CAN327 line discipline ID for ELM327 based CAN driver

The actual driver will be added via the CAN tree.

Acked-by: Marc Kleine-Budde mkl@pengutronix.de Signed-off-by: Max Staudt max@enpas.org Link: https://lore.kernel.org/r/20220618180134.9890-1-max@enpas.org Signed-off-by: Greg Kroah-Hartman gregkh@linuxfoundation.org

Input: usbtouchscreen - add driver_info sanity check

Add a sanity check on the device id-table driver_info field to make sure we never access a type structure (and function pointers) outside of the device info array (e.g. if someone fails to ifdef a device-id entry).

Note that this also suppresses a compiler warning with -Warray-bounds (gcc-11.3.0) when compile-testing the driver without enabling any of the device type Kconfig options:

drivers/input/touchscreen/usbtouchscreen.c: In function 'usbtouch_probe':
drivers/input/touchscreen/usbtouchscreen.c:1668:16:warning: array subscript <unknown> is outside array bounds of 'struct usbtouch_device_info[0]' [-Warray-bounds]
 1668 |         type = &usbtouch_dev_info[id->driver_info];

Signed-off-by: Johan Hovold johan@kernel.org Link: https://lore.kernel.org/r/20220623062446.16944-1-johan@kernel.org Signed-off-by: Dmitry Torokhov dmitry.torokhov@gmail.com

Created at 2 months ago
push

runtime: pass correct string to exits on Plan 9

In CL 405901 the definition of exit in the Plan 9 go runtime was changed like so:

-               status = append(itoa(tmp[:len(tmp)-1], uint64(e)), 0)
+               sl := itoa(tmp[:len(tmp)-1], uint64(e))
+               // Don't append, rely on the existing data being zero.
+               status = tmp[:len(sl)+1]

However, itoa only puts the converted number "somewhere" in the buffer. Specifically, it builds it from the end of the buffer towards the start, meaning the first byte of the buffer is a 0 byte, and the resulting string that's passed to exits is empty, leading to a falsely successful exit.

This change uses the returned value from itoa, rather than the buffer that was passed in, so that we start from the correct location in the string.

Fixes #53669

Change-Id: I63f0c7641fc6f55250857dc17a1eeb12ae0c2e10 Reviewed-on: https://go-review.googlesource.com/c/go/+/415680 Reviewed-by: David Chase drchase@google.com Reviewed-by: Ian Lance Taylor iant@google.com

build/constraint: update doc to mention a feature added in Go 1.17

The pkg documentation mentions that the "//go:build" syntax "will be" added in Go 1.17. In fact, it has been added in that Go release, so the documentation can now be updated.

Change-Id: I72f24063c3be62d97ca78bf724d56599f5f19460 GitHub-Last-Rev: 4371886f6ce9f2c2a370df047a5baa1f122c681f GitHub-Pull-Request: golang/go#53647 Reviewed-on: https://go-review.googlesource.com/c/go/+/415774 Reviewed-by: Ian Lance Taylor iant@google.com Run-TryBot: Ian Lance Taylor iant@google.com TryBot-Result: Gopher Robot gobot@golang.org Reviewed-by: Benny Siegert bsiegert@gmail.com Auto-Submit: Ian Lance Taylor iant@google.com

cmd/go: record origin metadata during module download

This change adds an "Origin" JSON key to the output of go list -json -m and go mod download -json. The associated value is a JSON object with metadata about the source control system. For Git, that metadata is sufficient to evaluate whether the remote server has changed in any interesting way that might invalidate the cached data. In most cases, it will not have, and a fetch could then avoid downloading a full repo from the server.

This origin metadata is also now recorded in the .info file for a given module@version, for informational and debugging purposes.

This change only adds the metadata. It does not use it to optimize away unnecessary git fetch operations. (That's the next change.)

For #53644.

Change-Id: I4a1712a2386d1d8ab4e02ffdf0f72ba75d556115 Reviewed-on: https://go-review.googlesource.com/c/go/+/411397 TryBot-Result: Gopher Robot gobot@golang.org Run-TryBot: Russ Cox rsc@golang.org Reviewed-by: Bryan Mills bcmills@google.com

cmd/go: add -reuse flag to make proxy invocations more efficient

The go list -m and go mod download commands now have a -reuse flag, which is passed the name of a file containing the JSON output from a previous run of the same command. (It is up to the caller to ensure that flags such as -versions or -retracted, which affect the output, are consistent between the old and new run.)

The new run uses the old JSON to evaluate whether the answer is unchanged since the old run. If so, it reuses that information, avoiding a costly 'git fetch', and sets a new Reuse: true field in its own JSON output.

This dance with saving the JSON output and passing it back to -reuse is not necessary on most systems, because the go command caches version control checkouts in the module cache. That cache means that a new 'git fetch' would only download the commits that are new since the previous one (often none at all).

The dance becomes important only on systems that do not preserve the module cache, for example by running 'go clean -modcache' aggressively or by running in some environment that starts with an empty file system.

For #53644.

Change-Id: I447960abf8055f83cc6dbc699a9fde9931130004 Reviewed-on: https://go-review.googlesource.com/c/go/+/411398 Run-TryBot: Russ Cox rsc@golang.org Reviewed-by: Bryan Mills bcmills@google.com

cmd/go: make module@nonexistentversion failures reusable

CL 411398 added the -reuse flag for reusing cached JSON output when the remote Git repository has not changed. One case that was not yet cached is a lookup of a nonexistent version.

This CL adds caching of failed lookups of nonexistent versions, by saving a checksum of all the heads and tags refs on the remote server (we never consider other kinds of refs). If none of those have changed, then we don't need to download the full server.

Fixes #53644.

Change-Id: I428bbc8ec8475bd7d03788934d643e1e2be3add0 Reviewed-on: https://go-review.googlesource.com/c/go/+/415678 Run-TryBot: Russ Cox rsc@golang.org Reviewed-by: Bryan Mills bcmills@google.com TryBot-Result: Gopher Robot gobot@golang.org

cmd/compile: drop "buildcfg" from no instrument packages

Package buildcfg was added to this list by CL 403851, but package buildcfg does not exist.

This was probably intended to refer to internal/buildcfg, but internal/buildcfg is only used by the compiler so it is not clear why it couldn't be instrumented.

For #44853.

Change-Id: Iad2517358be79c3eabf240376156bcff0c4bcefc Reviewed-on: https://go-review.googlesource.com/c/go/+/414516 Reviewed-by: Bryan Mills bcmills@google.com Reviewed-by: Cherry Mui cherryyz@google.com TryBot-Result: Gopher Robot gobot@golang.org Run-TryBot: Michael Pratt mpratt@google.com

test: recognize new gofrontend error message

The new gofrontend message matches other gofrontend error messages, so adjust the test to accept it.

For #27938 For #51237

Change-Id: I29b536f83a0cf22b1dbdae9abc2f5f6cf21d522d Reviewed-on: https://go-review.googlesource.com/c/go/+/416014 Run-TryBot: Ian Lance Taylor iant@golang.org Reviewed-by: Ian Lance Taylor iant@google.com TryBot-Result: Gopher Robot gobot@golang.org Reviewed-by: Than McIntosh thanm@google.com

misc/cgo/test: make TestSetgidStress cheaper

TestSetgidStress spawns 1000 threads, which can be expensive on some platforms or slow builders. Run with 50 threads in short mode instead.

This makes the failure less reproducible even with buggy code. But one can manually stress test it (e.g. when a flaky failure appear on the builder).

Fixes #53641.

Change-Id: I33b5ea5ecaa8c7a56f59c16f9171657ee295db47 Reviewed-on: https://go-review.googlesource.com/c/go/+/415677 Reviewed-by: Austin Clements austin@google.com TryBot-Result: Gopher Robot gobot@golang.org Run-TryBot: Cherry Mui cherryyz@google.com

cmd/dist: use purego tag when building the bootstrap binaries

This is in addition to the current math_big_pure_go tag. Using purego ensures that we can build the cmd binaries with gccgo.

For #53662

Change-Id: Ib82f8bf10659b5f94935f2b427ae8b2da875cd3b Reviewed-on: https://go-review.googlesource.com/c/go/+/415934 Reviewed-by: David Chase drchase@google.com Run-TryBot: Ian Lance Taylor iant@golang.org Reviewed-by: Ian Lance Taylor iant@google.com Run-TryBot: Ian Lance Taylor iant@google.com TryBot-Result: Gopher Robot gobot@golang.org Auto-Submit: Ian Lance Taylor iant@google.com

cmd/internal/notsha256: add purego tag as needed

This permits building the package with gccgo, when using gccgo as a bootstrap compiler.

Fixes #53662

Change-Id: Ic7ae9323ec5954e9306a32e1160e9aa1ed3aa202 Reviewed-on: https://go-review.googlesource.com/c/go/+/415935 TryBot-Result: Gopher Robot gobot@golang.org Run-TryBot: Ian Lance Taylor iant@google.com Auto-Submit: Ian Lance Taylor iant@google.com Reviewed-by: Ian Lance Taylor iant@google.com Reviewed-by: David Chase drchase@google.com

os/exec: clarify that Wait must be called

Fixes #52580

Change-Id: Ib2dd8a793b9c6fcb083abb3f7c346f6279adefc9 Reviewed-on: https://go-review.googlesource.com/c/go/+/414056 Run-TryBot: Ian Lance Taylor iant@golang.org TryBot-Result: Gopher Robot gobot@golang.org Reviewed-by: Alan Donovan adonovan@google.com Reviewed-by: Cherry Mui cherryyz@google.com

cmd/compile: rework induction variable detector

Induction variable detection is still not quite right. I've added another failing test.

Redo the overflow/underflow detector so it is more obviously correct.

Update #53600 Fixes #53653 Fixes #53663

Change-Id: Id95228e282fdbf6bd80b26e1c41d62e935ba08ff Reviewed-on: https://go-review.googlesource.com/c/go/+/415874 Run-TryBot: Keith Randall khr@golang.org TryBot-Result: Gopher Robot gobot@golang.org Reviewed-by: Russ Cox rsc@golang.org Reviewed-by: David Chase drchase@google.com

cmd/go: set up git identity for build_buildvcs_auto.txt

Just like in other tests like get_dotfiles.txt or version_buildvcs_git.txt. Without it, I get a failure on my machine:

fatal: empty ident name (for <mvdan@p14s.localdomain>) not allowed

Change-Id: I1c17c0d58c539b59154570b5438c7bd850bac5aa Reviewed-on: https://go-review.googlesource.com/c/go/+/416095 Reviewed-by: Ian Lance Taylor iant@google.com TryBot-Result: Gopher Robot gobot@golang.org Run-TryBot: Daniel Martí mvdan@mvdan.cc Reviewed-by: Dmitri Shuralyov dmitshur@google.com

cmd/compile: only check implicit dots for method call enabled by a type bound

Fixes #53419

Change-Id: Ibad64f5c4af2112deeb0a9ecc9c589b17594bd05 Reviewed-on: https://go-review.googlesource.com/c/go/+/414836 Reviewed-by: Matthew Dempsky mdempsky@google.com Reviewed-by: David Chase drchase@google.com Reviewed-by: Keith Randall khr@golang.org TryBot-Result: Gopher Robot gobot@golang.org Run-TryBot: Cuong Manh Le cuong.manhle.vn@gmail.com

cmd/go: default to "exe" build mode for windows -race

This patch changes the default build mode from "pie" to "exe" when building programs on windows with "-race" in effect. The Go command already issues an error if users explicitly ask for -buildmode=pie in combination with -race on windows, but wasn't revising the default "pie" build mode if a specific buildmode was not requested.

Updates #53539. Updates #35006.

Change-Id: I2f81a41a1d15a0b4f5ae943146175c5a1202cbe0 Reviewed-on: https://go-review.googlesource.com/c/go/+/416174 Reviewed-by: Alex Brainman alex.brainman@gmail.com Reviewed-by: Cherry Mui cherryyz@google.com TryBot-Result: Gopher Robot gobot@golang.org Run-TryBot: Than McIntosh thanm@google.com

cmd/link: explicitly disable PIE for windows/amd64 -race mode

Turn off PIE explicitly for windows/amd64 when -race is in effect, since at the moment the race detector runtime doesn't seem to handle PIE binaries correctly. Note that newer C compilers on windows produce PIE binaries by default, so the Go linker needs to explicitly turn off PIE when invoking the external linker in this case.

Updates #53539.

Change-Id: Ib990621f22cf61a5fa383584bab81d3dfd7552e8 Reviewed-on: https://go-review.googlesource.com/c/go/+/415676 Reviewed-by: Cherry Mui cherryyz@google.com TryBot-Result: Gopher Robot gobot@golang.org Run-TryBot: Than McIntosh thanm@google.com Reviewed-by: Alex Brainman alex.brainman@gmail.com

crypto/x509: populate Number and AKI of parsed CRLs

The x509.RevocationList type has two fields which correspond to extensions, rather than native fields, of the underlying ASN.1 CRL: the .Number field corresponds to the crlNumber extension, and the .AuthorityKeyId field corresponds to the authorityKeyIdentifier extension.

The x509.CreateRevocationList() function uses these fields to populate their respective extensions in the resulting CRL. However, the x509.ParseRevocationList() function does not perform the reverse operation: the fields retain their zero-values even after parsing a CRL which contains the relevant extensions.

Add code which populates these fields when parsing their extensions. Add assertions to the existing tests to confirm that the values are populated appropriately.

Fixes #53726

Change-Id: Ie5b71081e53034e0b5b9ff3c122065c62f15cf23 Reviewed-on: https://go-review.googlesource.com/c/go/+/416354 Run-TryBot: Roland Shoemaker roland@golang.org Auto-Submit: Roland Shoemaker roland@golang.org Reviewed-by: Roland Shoemaker roland@golang.org TryBot-Result: Gopher Robot gobot@golang.org Reviewed-by: Damien Neil dneil@google.com

crypto/x509: correctly parse CRL entry extensions

When checking to see if a CRL entry has any extensions, attempt to read them from the individual revokedCertificate, rather than from the parent TBSCertList.

Additionally, crlEntryExtensions is not an EXPLICIT field (c.f. crlExtension and Certificate extensions), so do not perform an extra layer of unwrapping when parsing the field.

The added test case fails without the accompanying changes.

Fixes #53592

Change-Id: Icc00e4c911f196aef77e3248117de64ddc5ea27f Reviewed-on: https://go-review.googlesource.com/c/go/+/414877 Reviewed-by: Damien Neil dneil@google.com Reviewed-by: Roland Shoemaker roland@golang.org Run-TryBot: Roland Shoemaker roland@golang.org Auto-Submit: Roland Shoemaker roland@golang.org TryBot-Result: Gopher Robot gobot@golang.org

crypto/x509: restrict CRL number to <=20 octets

Similar to certificate serial numbers, RFC 5280 restricts the length of the CRL number field to no more than 20 octets. Enforce this in CreateRevocationList.

Fixes #53543

Change-Id: If392ef6b0844db716ae9ee6ef317135fceab039c Reviewed-on: https://go-review.googlesource.com/c/go/+/415134 Auto-Submit: Roland Shoemaker roland@golang.org Reviewed-by: Tatiana Bradley tatiana@golang.org Reviewed-by: Damien Neil dneil@google.com TryBot-Result: Gopher Robot gobot@golang.org Run-TryBot: Roland Shoemaker roland@golang.org

runtime: overestimate the amount of allocated memory in heapLive

CL 377516 made it so that memory metrics are truly monotonic, but also updated how heapLive tracked allocated memory to also be monotonic.

The result is that cached spans with allocated memory aren't fully accounted for by the GC, causing it to make a worse assumption (the exact mechanism is at this time unknown), resulting in a memory regression, especially for smaller heaps.

This change is a partial revert of CL 377516 that makes heapLive a non-monotonic overestimate again, which appears to resolve the regression.

For #53738.

Change-Id: I5c51067abc0b8e0a6b89dd8dbd4a0be2e8c0c1b2 Reviewed-on: https://go-review.googlesource.com/c/go/+/416417 Reviewed-by: Michael Pratt mpratt@google.com Run-TryBot: Michael Knyszek mknyszek@google.com TryBot-Result: Gopher Robot gobot@golang.org

Created at 2 months ago

klish: File for intractive code

ktp: Working on tinyrl and client ktp

Merge branch 'master' of https://src.libcode.org/pkun/klish

ktp: ktp_sync_cmd()

ktp: Callbacks for some events

tinyrl mass refactoring. Unfinished. Buildable

Working on tinyrl. Unfinished

tinyrl: Char processing

tinyrl: tinyrl_line_insert()

tinyrl: Key delete and backspace

tinyrl: Move left and right

tinyrl: Fix utf8

tinyrl: Fix injection of char to line

tinyrl: First version of redisplay()

tinyrl: Key enter

tinyrl: Busy flag

Navigation command 'pop' exits process if pop from top level

konfd: Fix unclosed stderr descriptor

klish: Show error string from server

klish: Press enter with empty line

Created at 2 months ago

Use hashicorp/go-memdb instead of truncindex

memdb already knows how to search by prefix so there is no need to keep a separate list of container ids in the truncindex

Benchmarks:

$ go test -benchmem -run=^$ -count 5 -tags linux -bench ^BenchmarkDBGetByPrefix100$ github.com/docker/docker/container goos: linux goarch: amd64 pkg: github.com/docker/docker/container cpu: Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz BenchmarkDBGetByPrefix100-6 16018 73935 ns/op 33888 B/op 1100 allocs/op BenchmarkDBGetByPrefix100-6 16502 73150 ns/op 33888 B/op 1100 allocs/op BenchmarkDBGetByPrefix100-6 16218 74014 ns/op 33856 B/op 1100 allocs/op BenchmarkDBGetByPrefix100-6 15733 73370 ns/op 33792 B/op 1100 allocs/op BenchmarkDBGetByPrefix100-6 16432 72546 ns/op 33744 B/op 1100 allocs/op PASS ok github.com/docker/docker/container 9.752s

$ go test -benchmem -run=^$ -count 5 -tags linux -bench ^BenchmarkTruncIndexGet100$ github.com/docker/docker/pkg/truncindex goos: linux goarch: amd64 pkg: github.com/docker/docker/pkg/truncindex cpu: Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz BenchmarkTruncIndexGet100-6 16862 73732 ns/op 44776 B/op 1173 allocs/op BenchmarkTruncIndexGet100-6 16832 73629 ns/op 45184 B/op 1179 allocs/op BenchmarkTruncIndexGet100-6 17214 73571 ns/op 45160 B/op 1178 allocs/op BenchmarkTruncIndexGet100-6 16113 71680 ns/op 45360 B/op 1182 allocs/op BenchmarkTruncIndexGet100-6 16676 71246 ns/op 45056 B/op 1184 allocs/op PASS ok github.com/docker/docker/pkg/truncindex 9.759s

$ go test -benchmem -run=^$ -count 5 -tags linux -bench ^BenchmarkDBGetByPrefix500$ github.com/docker/docker/container goos: linux goarch: amd64 pkg: github.com/docker/docker/container cpu: Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz BenchmarkDBGetByPrefix500-6 1539 753541 ns/op 169381 B/op 5500 allocs/op BenchmarkDBGetByPrefix500-6 1624 749975 ns/op 169458 B/op 5500 allocs/op BenchmarkDBGetByPrefix500-6 1635 761222 ns/op 169298 B/op 5500 allocs/op BenchmarkDBGetByPrefix500-6 1693 727856 ns/op 169297 B/op 5500 allocs/op BenchmarkDBGetByPrefix500-6 1874 710813 ns/op 169570 B/op 5500 allocs/op PASS ok github.com/docker/docker/container 6.711s

$ go test -benchmem -run=^$ -count 5 -tags linux -bench ^BenchmarkTruncIndexGet500$ github.com/docker/docker/pkg/truncindex goos: linux goarch: amd64 pkg: github.com/docker/docker/pkg/truncindex cpu: Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz BenchmarkTruncIndexGet500-6 1934 780328 ns/op 224073 B/op 5929 allocs/op BenchmarkTruncIndexGet500-6 1713 713935 ns/op 225011 B/op 5937 allocs/op BenchmarkTruncIndexGet500-6 1780 702847 ns/op 224090 B/op 5943 allocs/op BenchmarkTruncIndexGet500-6 1736 711086 ns/op 224027 B/op 5929 allocs/op BenchmarkTruncIndexGet500-6 2448 508694 ns/op 222322 B/op 5914 allocs/op PASS ok github.com/docker/docker/pkg/truncindex 6.877s

Signed-off-by: Djordje Lukic djordje.lukic@docker.com

introduce Containerd-snapshotter feature flag

Signed-off-by: Nicolas De Loof nicolas.deloof@gmail.com

libnetwork: ipvlan: clean up some consts

Signed-off-by: Sebastiaan van Stijn github@gone.nl

libnetwork: macvlan: clean up some consts

Signed-off-by: Sebastiaan van Stijn github@gone.nl

libnetwork: ipvlan: use single ipSubnet type

Signed-off-by: Sebastiaan van Stijn github@gone.nl

libnetwork: macvlan: use single ipSubnet type

Signed-off-by: Sebastiaan van Stijn github@gone.nl

libnetwork: ipvlan: set network ID as part of parseNetworkOptions

Signed-off-by: Sebastiaan van Stijn github@gone.nl

libnetwork: ipvlan: processIPAM(): remove unused arg and error return

Signed-off-by: Sebastiaan van Stijn github@gone.nl

libnetwork: ipvlan: processIPAM(): simplify

Remove redundant checks and intermediate variables.

Signed-off-by: Sebastiaan van Stijn github@gone.nl

libnetwork: macvlan: set network ID as part of parseNetworkOptions

Signed-off-by: Sebastiaan van Stijn github@gone.nl

libnetwork: macvlan: processIPAM(): remove unused arg and error return

Signed-off-by: Sebastiaan van Stijn github@gone.nl

libnetwork: macvlan: processIPAM(): simplify

Remove redundant checks and intermediate variables.

Signed-off-by: Sebastiaan van Stijn github@gone.nl

libnetwork: macvlan: move validation into parseNetworkOptions()

Signed-off-by: Sebastiaan van Stijn github@gone.nl

libnetwork: ipvlan: move validation into parseNetworkOptions()

Signed-off-by: Sebastiaan van Stijn github@gone.nl

libnetwork: ipvlan: make configuration.fromOptions a constructor

This was effectively a constructor, but through some indirection; make it a regular function, which is a bit more idiomatic.

Signed-off-by: Sebastiaan van Stijn github@gone.nl

libnetwork: ipvlan: cleanup parseNetworkGenericOptions

Signed-off-by: Sebastiaan van Stijn github@gone.nl

libnetwork: macvlan: make configuration.fromOptions a constructor

This was effectively a constructor, but through some indirection; make it a regular function, which is a bit more idiomatic.

Signed-off-by: Sebastiaan van Stijn github@gone.nl

libnetwork: macvlan: cleanup parseNetworkGenericOptions

Signed-off-by: Sebastiaan van Stijn github@gone.nl

libnetwork: ipvlan: reduce use of const for driver name

Inlining the string makes the code more grep'able; renaming the const to "driverName" to reflect the remaining uses of it.

Signed-off-by: Sebastiaan van Stijn github@gone.nl

libnetwork: macvlan: reduce use of const for driver name

Inlining the string makes the code more grep'able; renaming the const to "driverName" to reflect the remaining uses of it.

Signed-off-by: Sebastiaan van Stijn github@gone.nl

Created at 2 months ago

DEVELOPERS: drop Gaël Portay

Gaël Portay is apparently no longer at Collabora:

gael.portay@collabora.com: host mail.collabora.co.uk[46.235.227.172] said: 550 5.1.1 gael.portay@collabora.com: Recipient address rejected: User unknown in local recipient table (in reply to RCPT TO command)

Signed-off-by: Thomas Petazzoni thomas.petazzoni@bootlin.com

boot/optee-os: fix typo in help message of BR2_TARGET_OPTEE_OS_CUSTOM_TARBALL

The custom tarball option should be given a URL pointing to an OP-TEE OS tarball and not a "kernel" one.

Fixes: 9c79b369d69c "boot/optee-os: add support for custom tarball URL" Cc: Quentin Schulz foss+buildroot@0leil.net Signed-off-by: Quentin Schulz quentin.schulz@theobroma-systems.com Signed-off-by: Yann E. MORIN yann.morin.1998@free.fr

package/python-setuptools-scm: add missing runtime dependency

Since version 7.0.4 python-setuptools-scm requires host-python-typing-extensions package.

Fixes: http://autobuild.buildroot.net/results/a4a52da24032222860ad6abe89bf66839cc2e812/ http://autobuild.buildroot.net/results/2b381cd32671db4aa0b281ece5569667bae0f923/ http://autobuild.buildroot.net/results/a3c5208224cc7825152d9a27b64fd82fb000a259/

Signed-off-by: Yegor Yefremov yegorslists@googlemail.com [yann.morin.1998@free.fr: split long line] Signed-off-by: Yann E. MORIN yann.morin.1998@free.fr

package/iptables: fix build with musl libc

Add upstream patch fixing collision of struct ethhdr definition with kernel headers.

Add another upstream patch to remove undefined u_int16_t type build breakage.

Fixes: http://autobuild.buildroot.net/results/2a449752ee51eed8b8d569a52eb69f635e0369cd/ http://autobuild.buildroot.net/results/23e97f88259850ecb12f2444365b34fa6fac8211/ http://autobuild.buildroot.net/results/b8e3809d469c949a755808b7132717b0325ebafa/

Signed-off-by: Baruch Siach baruch@tkos.co.il Signed-off-by: Yann E. MORIN yann.morin.1998@free.fr

package/libopenssl: security bump to version 1.1.1p

The c_rehash script allows command injection (CVE-2022-2068)

Severity: Moderate

In addition to the c_rehash shell command injection identified in CVE-2022-1292, further circumstances where the c_rehash script does not properly sanitise shell metacharacters to prevent command injection were found by code review.

When the CVE-2022-1292 was fixed it was not discovered that there are other places in the script where the file names of certificates being hashed were possibly passed to a command executed through the shell.

This script is distributed by some operating systems in a manner where it is automatically executed. On such operating systems, an attacker could execute arbitrary commands with the privileges of the script.

Use of the c_rehash script is considered obsolete and should be replaced by the OpenSSL rehash command line tool.

https://www.openssl.org/news/secadv/20220621.txt

Signed-off-by: Fabrice Fontaine fontaine.fabrice@gmail.com Signed-off-by: Yann E. MORIN yann.morin.1998@free.fr

package/uuu: add host-openssl dependency

Fix the following build failure raised since the addition of the package in commit 776385d645b37cfc43479b37e106244aa9ab2e85:

CMake Error: The following variables are used in this project, but they are set to NOTFOUND. Please set them or make sure they are set and tested correctly in the CMake files: OPENSSL_CRYPTO_LIBRARY (ADVANCED) linked by target "uuu" in directory /home/buildroot/autobuild/instance-0/output-1/build/host-uuu-1.4.193/uuu OPENSSL_SSL_LIBRARY (ADVANCED) linked by target "uuu" in directory /home/buildroot/autobuild/instance-0/output-1/build/host-uuu-1.4.193/uuu

Fixes:

  • http://autobuild.buildroot.org/results/2f05bc67112a59eba8f59ff707e43d76e41dbad1

Signed-off-by: Fabrice Fontaine fontaine.fabrice@gmail.com Reviewed-by: Dario Binacchi dario.binacchi@amarulasolutions.com Signed-off-by: Yann E. MORIN yann.morin.1998@free.fr

package/libcamera: strip symbols before signing IPA libs

Open-Source IPA shlibs need to be signed in order to be runnable within the same process, otherwise they are deemed Closed-Source and run in another process and communicate over IPC.

The shlib installed on the target should be the same as the one signed by libcamera during package creation otherwise the signature won't match the shlib.

Buildroot sanitizes RPATH in a post build process. meson gets rid of rpath while installing so we don't need to do it manually.

Buildroot may strip symbols, so we need to do the same before signing.

Signing the IPA shlibs is done by the meson install target, so we need to strip the IPA shlibs, so after the build but before the install, which a post-build hooks fits the best.

Cc: Quentin Schulz foss+buildroot@0leil.net Signed-off-by: Quentin Schulz quentin.schulz@theobroma-systems.com [yann.morin.1998@free.fr: slight rewording of commit log] Signed-off-by: Yann E. MORIN yann.morin.1998@free.fr

package/libostree: bump to version 2022.4

Signed-off-by: Marcus Folkesson marcus.folkesson@gmail.com Signed-off-by: Thomas Petazzoni thomas.petazzoni@bootlin.com

package/uuu: bump to version 1.4.224

It requires the host-zstd package.

The hash of README.md changed due to changes unrelated to the license terms:

-- sudo apt-get install libusb-1.0-0-dev libbz2-dev pkg-config cmake libssl-dev g++ +- sudo apt-get install libusb-1.0-0-dev libbz2-dev libzstd-dev pkg-config cmake libssl-dev g++

Signed-off-by: Dario Binacchi dario.binacchi@amarulasolutions.com Signed-off-by: Thomas Petazzoni thomas.petazzoni@bootlin.com

package/libyang: bump version to 2.0.194

Signed-off-by: Heiko Thiery heiko.thiery@gmail.com Signed-off-by: Thomas Petazzoni thomas.petazzoni@bootlin.com

package/sysrepo: bump version to 2.1.64

Signed-off-by: Heiko Thiery heiko.thiery@gmail.com Signed-off-by: Thomas Petazzoni thomas.petazzoni@bootlin.com

package/libnetconf2: bump version to 2.1.11

Signed-off-by: Heiko Thiery heiko.thiery@gmail.com Signed-off-by: Thomas Petazzoni thomas.petazzoni@bootlin.com

package/netopeer2: bump version to 2.1.23

Add patch to fix issue building with buildroot. The patch is already accepted upstream.

Signed-off-by: Heiko Thiery heiko.thiery@gmail.com Signed-off-by: Thomas Petazzoni thomas.petazzoni@bootlin.com

package/libgpgme: fix LIBGPGME_CPE_ID_PRODUCT

Fix typo added by commit 6b79c8fb05bf1ae569d8b8e8c9f6f516e97c9ae0

Signed-off-by: Fabrice Fontaine fontaine.fabrice@gmail.com Signed-off-by: Thomas Petazzoni thomas.petazzoni@bootlin.com

package/keyutils: add KEYUTILS_CPE_ID_VENDOR

cpe:2.3:a:keyutils_project:keyutils is a valid CPE identifier for this package:

https://nvd.nist.gov/products/cpe/search/results?namingFormat=2.3&keyword=cpe%3A2.3%3Aa%3Akeyutils_project%3Akeyutils

Signed-off-by: Fabrice Fontaine fontaine.fabrice@gmail.com Signed-off-by: Thomas Petazzoni thomas.petazzoni@bootlin.com

package/isl: bump to version 0.24

https://repo.or.cz/isl.git/blob/3ea3e8b77475bea49b35b8215d8f66af94121b3c:/ChangeLog

Signed-off-by: Fabrice Fontaine fontaine.fabrice@gmail.com Signed-off-by: Thomas Petazzoni thomas.petazzoni@bootlin.com

package/memtester: bump to version 4.5.1

https://pyropus.ca./software/memtester/CHANGELOG

Signed-off-by: Fabrice Fontaine fontaine.fabrice@gmail.com Signed-off-by: Thomas Petazzoni thomas.petazzoni@bootlin.com

package/inih: bump to version 55

https://github.com/benhoyt/inih/releases/tag/r54 https://github.com/benhoyt/inih/releases/tag/r55

Signed-off-by: Fabrice Fontaine fontaine.fabrice@gmail.com Signed-off-by: Thomas Petazzoni thomas.petazzoni@bootlin.com

package/libva: bump version to 2.15.0

Release notes: https://github.com/intel/libva/blob/v2.15-branch/NEWS

Signed-off-by: Bernd Kuhls bernd.kuhls@t-online.de Signed-off-by: Thomas Petazzoni thomas.petazzoni@bootlin.com

package/libva-utils: bump version to 2.15.0

Signed-off-by: Bernd Kuhls bernd.kuhls@t-online.de Signed-off-by: Thomas Petazzoni thomas.petazzoni@bootlin.com

Created at 2 months ago

Increase timeout waiting for OVN startup

We see some cases where OVN startup takes much longer than 5 seconds, up to 28 seconds have been observed, so increase the limit to 40 to be on the safe side.

Signed-off-by: Dr. Jens Harbott harbott@osism.tech Closes-Bug: 1980421 Change-Id: I6da4a537e6a8d527ff71a821f07164fc7d342882

Created at 2 months ago

Fix bug where function args with side effects were sometimes deleted

When OptimizeParameters moved a side-effectful function argument into the function body itself, e.g. f(console.log("calling f")); function f() {} to f(); function f() { console.log("calling f"); }

it failed to annotate the call f(); as having side effects. This could cause later passes to dead-code eliminate f() entirely.

PiperOrigin-RevId: 459293156

Add missing @CanIgnoreReturnValue annotation to j2cl version of Hasher.

PiperOrigin-RevId: 459307229

Documenting the current state of the control flow graph for unreachable static blocks.

Commented the expected behavior for test.

PiperOrigin-RevId: 459380575

Update ASTValidator to allow super property references in class static blocks.

PiperOrigin-RevId: 459531616

Reformatting control flow analysis

PiperOrigin-RevId: 459567526

Do not allow certain keywords to be used directly inside class static blocks: yield, await, break, continue

PiperOrigin-RevId: 459601066

updated TODO bug

PiperOrigin-RevId: 459607246

Add @Nullable annotation to methods that return null

PiperOrigin-RevId: 459629063

Fix getClosestContainerScope() to support class static blocks

PiperOrigin-RevId: 459634156

Assume reflected properties are referenced

Fix TypedScopeCreator to support class static blocks

PiperOrigin-RevId: 459752185

Fix bug where types shadowing goog.module imports were not resolved

PiperOrigin-RevId: 459802577

Replace onSomeParent with onClosestContainerScope on some SyntacticScopeCreator test cases for class static blocks

PiperOrigin-RevId: 459828668

Add support for class static blocks in serializer

PiperOrigin-RevId: 459862921

chore: sync changes for Maps JS API v3.49.8.

PiperOrigin-RevId: 459872774

Add repro for buggy edge case in class computed field execution order

PiperOrigin-RevId: 460314060

Make 2-lines module declarations recognizable by JsFileRegexParser.

PiperOrigin-RevId: 460485240

Add class static block tests to TypeCheckNoTranspileTest

PiperOrigin-RevId: 460495518

Stop serializing Compiler#changeStamp

Since we aren't serializing the corresponding properties on the AST nodes, there's no benefit in serializing changeStamp between stages. We can just re-initialize it to 1 when restoring state.

Also, it turns out that for some unknown reason the value of changeStamp isn't deterministic, which made the .save file contents non-deterministic, which caused problems for build systems using closure-compiler.

PiperOrigin-RevId: 460527162

Use LinkedHashMap instead of IdentityHashMap in RemoveUnusedCode

Using IdentityHashMap was unnecessary, because the Var class used as a key uses identity equals semantics anyway.

Using LinkedHashMap makes the iteration over the variables being considered deterministic, which helps ensure the compiler's output is deterministic.

PiperOrigin-RevId: 460720824

Created at 2 months ago

lineedit: get PWD from ash

The line editing code and ash disagree when the current directory is changed to a symbolic link:

~ $ mkdir real ~ $ ln -s real link ~ $ cd link ~/real $ pwd /home/rmyf36/link

Note the prompt says we're in ~/real. Bash does:

[rmy@random ~]$ cd link [rmy@random link]$ pwd /home/rmyf36/link

Ash uses the name supplied by the user while the line editing code calls getcwd(3). The discrepancy can be avoided by fetching the value of PWD from ash.

Hush calls getcwd(3) when the directory is changed so there's no disagreement with the line editing code.

There is no standard how shells should handle cd'ing into symlinks.

function old new delta parse_and_put_prompt 838 869 +31

Signed-off-by: Ron Yorston rmy@pobox.com Signed-off-by: Denys Vlasenko vda.linux@googlemail.com

shaNNNsum: accept one-space "HASH FILENAME" format for -c, closes 14866

function old new delta md5_sha1_sum_main 496 501 +5

Signed-off-by: Denys Vlasenko vda.linux@googlemail.com

awk: fix use after free (CVE-2022-30065)

fixes https://bugs.busybox.net/show_bug.cgi?id=14781

function old new delta evaluate 3343 3357 +14

Signed-off-by: Natanael Copa ncopa@alpinelinux.org Signed-off-by: Denys Vlasenko vda.linux@googlemail.com

tls: P256: remove NOP macro sp_256_norm_8()

Signed-off-by: Denys Vlasenko vda.linux@googlemail.com

udhcpc6: add missed big-endian conversions

function old new delta option_to_env 686 694 +8

Signed-off-by: Denys Vlasenko vda.linux@googlemail.com

Created at 2 months ago

deploy api script to upload certs to proxmox using proxmox api

fixed per shellcheck's preference for -n instead of ! -z

properly quoted variable names

shell check war warning against unnecessary use of cat

Update proxmoxve.sh

fixed to use _post function instead of curl

typo, using _H1 to provide header keys.

added _getdeployconf to set all of the environment variables

sensititive things debugged at a higher level

not generating files any more

typo

those where flipped by mistake

debugging for the payload

seems like the escaped new lines aren't remaining escaped new lines with the new version of curl

Revert "seems like the escaped new lines aren't remaining escaped new lines with the new version of curl"

This reverts commit a5d5113be34bace02dc9370bed102187aa52e7fe.

'+' are being converted to ' ' at some point

Revert "'+' are being converted to ' ' at some point"

This reverts commit 149310e1ecdec3343757296cab9ebf6975693d5d.

forced content-type to json

Merge branch 'proxmoxve' of github.com:wsellitti/acme.sh into proxmoxve

Merge branch 'proxmoxve' of gitlab.lan.home.wesitcllc.com:software/upstream/acme.sh into proxmoxve

Created at 2 months ago
Created at 2 months ago
Created at 2 months ago
create tag
nawawi create tag v22.07.01
Created at 2 months ago

bump 22.07.01

  • Fixed: Plugin:cleanuppost() -> Invalid index for trashbin.
  • Fixed: MoCache() -> Add $entries, $headers properties to avoid warning on get_translations_for_domain.
  • Updated: Symfony component -> symfony/var-exporter.
Created at 2 months ago
Created at 2 months ago

MAINTAINERS: Update Intel pin control to Supported

The actual status of the code is Supported.

Reported-by: dave.hansen@linux.intel.com Signed-off-by: Andy Shevchenko andriy.shevchenko@linux.intel.com Acked-by: Mika Westerberg mika.westerberg@linux.intel.com

Merge tag 'v5.19-rc1' into asoc-5.19

Linux 5.19-rc1

ASoC: ops: Fix off by one in range control validation

We currently report that range controls accept a range of 0..(max-min) but accept writes in the range 0..(max-min+1). Remove that extra +1.

Signed-off-by: Mark Brown broonie@kernel.org Link: https://lore.kernel.org/r/20220604105246.4055214-1-broonie@kernel.org Signed-off-by: Mark Brown broonie@kernel.org

dmaengine: ti: Fix refcount leak in ti_dra7_xbar_route_allocate

of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when not needed anymore.

Add missing of_node_put() in to fix this.

Fixes: ec9bfa1e1a79 ("dmaengine: ti-dma-crossbar: dra7: Use bitops instead of idr") Signed-off-by: Miaoqian Lin linmq006@gmail.com Link: https://lore.kernel.org/r/20220605042723.17668-2-linmq006@gmail.com Signed-off-by: Vinod Koul vkoul@kernel.org

dmaengine: ti: Add missing put_device in ti_dra7_xbar_route_allocate

of_find_device_by_node() takes reference, we should use put_device() to release it when not need anymore.

Fixes: a074ae38f859 ("dmaengine: Add driver for TI DMA crossbar on DRA7x") Signed-off-by: Miaoqian Lin linmq006@gmail.com Acked-by: Peter Ujfalusi peter.ujfalusi@gmail.com Link: https://lore.kernel.org/r/20220605042723.17668-1-linmq006@gmail.com Signed-off-by: Vinod Koul vkoul@kernel.org

dmaengine: Revert "dmaengine: add verification of DMA_INTERRUPT capability for dmatest"

This reverts commit a8facc7b9885 ("dmaengine: add verification of DMA_INTERRUPT capability for dmatest") as it causes regression due to the fact that DMA_INTERRUPT in linked to dma_prep_interrupt() so checking that is incorrect here

Signed-off-by: Vinod Koul vkoul@kernel.org Link: https://lore.kernel.org/r/20220606174906.3979283-1-vkoul@kernel.org Signed-off-by: Vinod Koul vkoul@kernel.org

dmaengine: imx-sdma: Allow imx8m for imx7 FW revs

The revision of the imx-sdma IP that is in the i.MX8M series is the same is that as that in the i.MX7 series but the imx7d MODULE_FIRMWARE directive is wrapped in a condiditional which means it's not defined when built for aarch64 SOC_IMX8M platforms and hence you get the following errors when the driver loads on imx8m devices:

imx-sdma 302c0000.dma-controller: Direct firmware load for imx/sdma/sdma-imx7d.bin failed with error -2 imx-sdma 302c0000.dma-controller: external firmware not found, using ROM firmware

Add the SOC_IMX8M into the check so the firmware can load on i.MX8.

Fixes: 1474d48bd639 ("arm64: dts: imx8mq: Add SDMA nodes") Fixes: 941acd566b18 ("dmaengine: imx-sdma: Only check ratio on parts that support 1:1") Signed-off-by: Peter Robinson pbrobinson@gmail.com Cc: stable@vger.kernel.org # v5.2+ Reviewed-by: Fabio Estevam festevam@gmail.com Link: https://lore.kernel.org/r/20220606161034.3544803-1-pbrobinson@gmail.com Signed-off-by: Vinod Koul vkoul@kernel.org

ARM: meson: Fix refcount leak in meson_smp_prepare_cpus

of_find_compatible_node() returns a node pointer with refcount incremented, we should use of_node_put() on it when done. Add missing of_node_put() to avoid refcount leak.

Fixes: d850f3e5d296 ("ARM: meson: Add SMP bringup code for Meson8 and Meson8b") Signed-off-by: Miaoqian Lin linmq006@gmail.com Reviewed-by: Martin Blumenstingl martin.blumenstingl@googlemail.com Signed-off-by: Neil Armstrong narmstrong@baylibre.com Link: https://lore.kernel.org/r/20220512021611.47921-1-linmq006@gmail.com

pinctrl: aspeed: Fix potential NULL dereference in aspeed_pinmux_set_mux()

pdesc could be null but still dereference pdesc->name and it will lead to a null pointer access. So we move a null check before dereference.

Signed-off-by: Haowen Bai baihaowen@meizu.com Link: https://lore.kernel.org/r/1650508019-22554-1-git-send-email-baihaowen@meizu.com Signed-off-by: Linus Walleij linus.walleij@linaro.org

pinctrl: sunxi: a83t: Fix NAND function name for some pins

The other NAND pins on Port C use the "nand0" function name. "nand0" also matches all of the other Allwinner SoCs.

Fixes: 4730f33f0d82 ("pinctrl: sunxi: add allwinner A83T PIO controller support") Signed-off-by: Samuel Holland samuel@sholland.org Acked-by: Jernej Skrabec jernej.skrabec@gmail.com Link: https://lore.kernel.org/r/20220526024956.49500-1-samuel@sholland.org Signed-off-by: Linus Walleij linus.walleij@linaro.org

Merge tag 'intel-pinctrl-v5.19-3' of gitolite.kernel.org:pub/scm/linux/kernel/git/pinctrl/intel into fixes

intel-pinctrl for v5.19-3

  • Update a record in the MAINTAINERS database for Intel pin control drivers

The following is an automated git shortlog grouped by driver:

MAINTAINERS:

  • Update Intel pin control to Supported

irqchip/gicv3: Handle resource request failure consistently

Due to a silly oversight on my part, making the simple switch to of_io_request_and_map() in the DT path inadvertently introduced divergent behaviour, whereby failng to request an iomem region now becomes fatal for DT, vs. being silently ignored for ACPI.

Refactor a bit harder, so that request errors are non-fatal in both paths as intended, but also consistently reported as well.

Reported-by: Matt Ranostay mranostay@ti.com Fixes: 2b2cd74a06c3 ("irqchip/gic-v3: Claim iomem resources") Signed-off-by: Robin Murphy robin.murphy@arm.com Signed-off-by: Marc Zyngier maz@kernel.org Link: https://lore.kernel.org/r/5f2b57a0131f3082fae9d3002d360bf784ccb092.1655387206.git.robin.murphy@arm.com

ARM: dts: imx7d-smegw01: Fix the SDIO description

usdhc2 is connected to a Wifi chip that is powered by a 3.3V supply.

Pass the "no-1-8-v" property to guarantee that no communication is made at 1.8V.

While at it, also remove the unnecessary properties: "cap-sd-highspeed", "sd-uhs-ddr50", and "mmc-ddr-1_8v".

Fixes: 9ac0ae97e349 ("ARM: dts: imx7d-smegw01: Add support for i.MX7D SMEGW01 board") Signed-off-by: Fabio Estevam festevam@denx.de Signed-off-by: Shawn Guo shawnguo@kernel.org

firmware: arm_scmi: Relax CLOCK_DESCRIBE_RATES out-of-spec checks

A reply to CLOCK_DESCRIBE_RATES issued against a non rate-discrete clock should be composed of a triplet of rates descriptors (min/max/step) returned all in one reply message.

This is not always the case when dealing with some SCMI server deployed in the wild: relax such constraint while maintaining memory safety by checking carefully the returned payload size.

While at that cleanup a stale debug printout.

Link: https://lore.kernel.org/r/20220616170347.2800771-1-cristian.marussi@arm.com Fixes: 7bc7caafe6b1 ("firmware: arm_scmi: Use common iterators in the clock protocol") Tested-by: Robin Murphy robin.murphy@arm.com Signed-off-by: Cristian Marussi cristian.marussi@arm.com Signed-off-by: Sudeep Holla sudeep.holla@arm.com

arm64: dts: qcom: Remove duplicate sc7180-trogdor include on lazor/homestar

The sc7180-trogdor-{lazor,homestar}-*.dtsi files all include sc7180-trogdor.dtsi and sc7180-trogdor-lazor.dtsi or sc7180-trogdor-homestar.dtsi, so including it here in the sc7180-trogdor-{lazor,homestar}.dtsi file means we have a duplicate include after commit 19794489fa24 ("arm64: dts: qcom: Only include sc7180.dtsi in sc7180-trogdor.dtsi"). We include the sc7180-trogdor.dtsi file in a board like sc7180-trogdor-lazor-r1.dts so that we can include the display bridge snippet (e.g. sc7180-trogdor-ti-sn65dsi86.dtsi) instead of making ever increasing variants like sc7180-trogdor-lazor-ti-sn65dsi86.dtsi.

Unfortunately, having the double include like this means the display bridge's i2c bus is left disabled instead of enabled by the bridge snippet. Any boards that use the i2c bus for the display bridge will have the bus disabled when we include sc7180-trogdor.dtsi the second time, which picks up the i2c status="disabled" line from sc7180.dtsi. This leads to the display not turning on and black screens at boot on lazor and homestar devices.

Fix this by dropping the include and making a note that the sc7180-trogdor-{lazor,homestar}.dtsi file must be included after sc7180-trogdor.dtsi

Reported-by: Douglas Anderson dianders@chromium.org Cc: "Joseph S. Barrera III" joebar@chromium.org Cc: Matthias Kaehlcke mka@chromium.org Fixes: 19794489fa24 ("arm64: dts: qcom: Only include sc7180.dtsi in sc7180-trogdor.dtsi") Signed-off-by: Stephen Boyd swboyd@chromium.org Reviewed-by: Douglas Anderson dianders@chromium.org Tested-by: Douglas Anderson dianders@chromium.org Signed-off-by: Bjorn Andersson bjorn.andersson@linaro.org Link: https://lore.kernel.org/r/20220602190621.1646679-1-swboyd@chromium.org

MAINTAINERS: Update Ben's email address

I'm leaving Intel. Update email address to korg and add .mailmap entries. For now, I will be taking a reduced role in CXL development, but I still plan to spend time working on it, and I can still serve as a good substitute if needed for maintainer responsibilities (that may change in the future).

Signed-off-by: Ben Widawsky ben.widawsky@intel.com Reviewed-by: Alison Schofield alison.schofield@intel.com Link: https://lore.kernel.org/r/20220520180059.632054-1-bwidawsk@kernel.org Signed-off-by: Dan Williams dan.j.williams@intel.com

cxl: Fix cleanup of port devices on failure to probe driver.

The device is created, and then there is a check if a driver succesfully bound to it. In event of failing the bind (e.g. failure in cxl_port_probe()) the device is left registered. When a bus rescan later occurs, fresh devices are created leading to a multiple device representing the same underlying hardware. Bad things may follow and at very least we have far too many devices.

Fix by ensuring autoremove is registered if the device create succeeds, but doesn't depend on sucessful binding to a driver.

Bug was observed as side effect of incorrect ownership in [PATCH v9 6/9] cxl/port: Read CDAT table but will result from any failure to in cxl_port_probe().

Fixes: 8dd2bc0f8e02 ("cxl/mem: Add the cxl_mem driver") Signed-off-by: Jonathan Cameron Jonathan.Cameron@huawei.com Reviewed-by: Ira Weiny ira.weiny@intel.com Link: https://lore.kernel.org/r/20220609134519.11668-1-Jonathan.Cameron@huawei.com Signed-off-by: Dan Williams dan.j.williams@intel.com

cxl/core: Use is_endpoint_decoder

Save some characters and directly check decoder type rather than port type. There's no need to check if the port is an endpoint port since, by this point, cxl_endpoint_decoder_alloc() has a specified type.

Reviewed by: Adam Manzanares a.manzanares@samsung.com Signed-off-by: Ben Widawsky ben.widawsky@intel.com Signed-off-by: Dan Williams dan.j.williams@intel.com

cxl/mbox: Use __le32 in get,set_lsa mailbox structures

CXL specification defines these as little endian.

Fixes: 60b8f17215de ("cxl/pmem: Translate NVDIMM label commands to CXL label commands") Reported-by: Dan Williams dan.j.williams@intel.com Signed-off-by: Alison Schofield alison.schofield@intel.com Link: https://lore.kernel.org/r/20220225221456.1025635-1-alison.schofield@intel.com Signed-off-by: Dan Williams dan.j.williams@intel.com

ipc: Free mq_sysctls if ipc namespace creation failed

The problem that Dmitry Vyukov pointed out is that if setup_ipc_sysctls fails, mq_sysctls must be freed before return.

executing program BUG: memory leak unreferenced object 0xffff888112fc9200 (size 512): comm "syz-executor237", pid 3648, jiffies 4294970469 (age 12.270s) hex dump (first 32 bytes): ef d3 60 85 ff ff ff ff 0c 9b d2 12 81 88 ff ff ..`............. 04 00 00 00 a4 01 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [] kmemdup+0x23/0x50 mm/util.c:129 [] kmemdup include/linux/fortify-string.h:456 [inline] [] setup_mq_sysctls+0x4b/0x1c0 ipc/mq_sysctl.c:89 [] create_ipc_ns ipc/namespace.c:63 [inline] [] copy_ipcs+0x292/0x390 ipc/namespace.c:91 [] create_new_namespaces+0xdc/0x4f0 kernel/nsproxy.c:90 [] unshare_nsproxy_namespaces+0x9b/0x120 kernel/nsproxy.c:226 [] ksys_unshare+0x2fe/0x600 kernel/fork.c:3165 [] __do_sys_unshare kernel/fork.c:3236 [inline] [] __se_sys_unshare kernel/fork.c:3234 [inline] [] __x64_sys_unshare+0x12/0x20 kernel/fork.c:3234 [] do_syscall_x64 arch/x86/entry/common.c:50 [inline] [] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 [] entry_SYSCALL_64_after_hwframe+0x46/0xb0

BUG: memory leak unreferenced object 0xffff888112fd5f00 (size 256): comm "syz-executor237", pid 3648, jiffies 4294970469 (age 12.270s) hex dump (first 32 bytes): 00 92 fc 12 81 88 ff ff 00 00 00 00 01 00 00 00 ................ 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [] kmalloc include/linux/slab.h:605 [inline] [] kzalloc include/linux/slab.h:733 [inline] [] __register_sysctl_table+0x7b/0x7f0 fs/proc/proc_sysctl.c:1344 [] setup_mq_sysctls+0x12a/0x1c0 ipc/mq_sysctl.c:112 [] create_ipc_ns ipc/namespace.c:63 [inline] [] copy_ipcs+0x292/0x390 ipc/namespace.c:91 [] create_new_namespaces+0xdc/0x4f0 kernel/nsproxy.c:90 [] unshare_nsproxy_namespaces+0x9b/0x120 kernel/nsproxy.c:226 [] ksys_unshare+0x2fe/0x600 kernel/fork.c:3165 [] __do_sys_unshare kernel/fork.c:3236 [inline] [] __se_sys_unshare kernel/fork.c:3234 [inline] [] __x64_sys_unshare+0x12/0x20 kernel/fork.c:3234 [] do_syscall_x64 arch/x86/entry/common.c:50 [inline] [] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 [] entry_SYSCALL_64_after_hwframe+0x46/0xb0

BUG: memory leak unreferenced object 0xffff888112fbba00 (size 256): comm "syz-executor237", pid 3648, jiffies 4294970469 (age 12.270s) hex dump (first 32 bytes): 78 ba fb 12 81 88 ff ff 00 00 00 00 01 00 00 00 x............... 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [] kmalloc include/linux/slab.h:605 [inline] [] kzalloc include/linux/slab.h:733 [inline] [] new_dir fs/proc/proc_sysctl.c:978 [inline] [] get_subdir fs/proc/proc_sysctl.c:1022 [inline] [] __register_sysctl_table+0x5a9/0x7f0 fs/proc/proc_sysctl.c:1373 [] setup_mq_sysctls+0x12a/0x1c0 ipc/mq_sysctl.c:112 [] create_ipc_ns ipc/namespace.c:63 [inline] [] copy_ipcs+0x292/0x390 ipc/namespace.c:91 [] create_new_namespaces+0xdc/0x4f0 kernel/nsproxy.c:90 [] unshare_nsproxy_namespaces+0x9b/0x120 kernel/nsproxy.c:226 [] ksys_unshare+0x2fe/0x600 kernel/fork.c:3165 [] __do_sys_unshare kernel/fork.c:3236 [inline] [] __se_sys_unshare kernel/fork.c:3234 [inline] [] __x64_sys_unshare+0x12/0x20 kernel/fork.c:3234 [] do_syscall_x64 arch/x86/entry/common.c:50 [inline] [] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 [] entry_SYSCALL_64_after_hwframe+0x46/0xb0

BUG: memory leak unreferenced object 0xffff888112fbb900 (size 256): comm "syz-executor237", pid 3648, jiffies 4294970469 (age 12.270s) hex dump (first 32 bytes): 78 b9 fb 12 81 88 ff ff 00 00 00 00 01 00 00 00 x............... 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [] kmalloc include/linux/slab.h:605 [inline] [] kzalloc include/linux/slab.h:733 [inline] [] new_dir fs/proc/proc_sysctl.c:978 [inline] [] get_subdir fs/proc/proc_sysctl.c:1022 [inline] [] __register_sysctl_table+0x5a9/0x7f0 fs/proc/proc_sysctl.c:1373 [] setup_mq_sysctls+0x12a/0x1c0 ipc/mq_sysctl.c:112 [] create_ipc_ns ipc/namespace.c:63 [inline] [] copy_ipcs+0x292/0x390 ipc/namespace.c:91 [] create_new_namespaces+0xdc/0x4f0 kernel/nsproxy.c:90 [] unshare_nsproxy_namespaces+0x9b/0x120 kernel/nsproxy.c:226 [] ksys_unshare+0x2fe/0x600 kernel/fork.c:3165 [] __do_sys_unshare kernel/fork.c:3236 [inline] [] __se_sys_unshare kernel/fork.c:3234 [inline] [] __x64_sys_unshare+0x12/0x20 kernel/fork.c:3234 [] do_syscall_x64 arch/x86/entry/common.c:50 [inline] [] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 [] entry_SYSCALL_64_after_hwframe+0x46/0xb0

Reported-by: syzbot+b4b0d1b35442afbf6fd2@syzkaller.appspotmail.com Signed-off-by: Alexey Gladkov legion@kernel.org Link: https://lkml.kernel.org/r/000000000000f5004705e1db8bad@google.com Link: https://lkml.kernel.org/r/20220622200729.2639663-1-legion@kernel.org Signed-off-by: Eric W. Biederman ebiederm@xmission.com

Created at 2 months ago