labels: ["pkgsite"]
body:
  - type: markdown
    attributes:
      value: "Please answer these questions before submitting your issue. Thanks!"
  - type: input
    id: url
    attributes:
      label: "What is the URL of the page with the issue?"
    validations:
      required: true
  - type: input
    id: user-agent
    attributes:
      label: "What is your user agent?"

package bytes_test

import (
	. "bytes"
	"syscall"
	"testing"
)

// This file tests the situation where byte operations are checking
// data very near to a page boundary. We want to make sure those
// operations do not read across the boundary and cause a page
// fault where they shouldn't.

// These tests run only on linux. The code being tested is
// not OS-specific, so it does not need to be tested on all
// operating systems.

pkg debug/elf, const R_MIPS_GOT_LO16 = 23
pkg debug/elf, const R_MIPS_GOT_LO16 R_MIPS
pkg debug/elf, const R_MIPS_GOT_OFST = 21
pkg debug/elf, const R_MIPS_GOT_OFST R_MIPS
pkg debug/elf, const R_MIPS_GOT_PAGE = 20
pkg debug/elf, const R_MIPS_GOT_PAGE R_MIPS
pkg debug/elf, const R_MIPS_GPREL16 = 7
pkg debug/elf, const R_MIPS_GPREL16 R_MIPS
pkg debug/elf, const R_MIPS_GPREL32 = 12
pkg debug/elf, const R_MIPS_GPREL32 R_MIPS

			if pos != -1 {
				t.Errorf("IndexByte(%q, 'x') = %v", b1, pos)
			}
		}
	}
}

// test a small index across all page offsets
func TestIndexByteSmall(t *testing.T) {
	b := make([]byte, 5015) // bigger than a page
	// Make sure we find the correct byte even when straddling a page.
	for i := 0; i <= len(b)-15; i++ {
		for j := 0; j < 15; j++ {
			b[i+j] = byte(100 + j)
		}
		for j := 0; j < 15; j++ {

pkg syscall (windows-386), const PAGE_EXECUTE_READ ideal-int
pkg syscall (windows-386), const PAGE_EXECUTE_READWRITE ideal-int
pkg syscall (windows-386), const PAGE_EXECUTE_WRITECOPY ideal-int
pkg syscall (windows-386), const PAGE_READONLY ideal-int
pkg syscall (windows-386), const PAGE_READWRITE ideal-int
pkg syscall (windows-386), const PAGE_WRITECOPY ideal-int

      description: |
        We can remove packages with a shared path prefix.
        For example, a request for 'github.com/author' would remove all pkg.go.dev pages with that package path prefix.
    validations:
      required: true
  - type: textarea
    id: package-owner
    attributes:
      label: "Are you the owner of this package?"
      description: |

pkg syscall (darwin-arm64), const MADV_WILLNEED = 3
pkg syscall (darwin-arm64), const MADV_WILLNEED ideal-int
pkg syscall (darwin-arm64), const MADV_ZERO_WIRED_PAGES = 6
pkg syscall (darwin-arm64), const MADV_ZERO_WIRED_PAGES ideal-int
pkg syscall (darwin-arm64), const MAP_ANON = 4096
pkg syscall (darwin-arm64), const MAP_ANON ideal-int
pkg syscall (darwin-arm64), const MAP_COPY = 2

Go 1.22 changed how the runtime interacts with transparent huge pages on Linux.
In particular, a common default Linux kernel configuration can result in
significant memory overheads, and Go 1.22 no longer works around this default.
To work around this issue without adjusting kernel settings, transparent huge
pages can be disabled for Go memory with the
[`disablethp` setting](/pkg/runtime#hdr-Environment_Variable).

{
  "name": "Hacking Gopher",
  "version": "1.0",
  "manifest_version": 2,
  "description": "Go Hacking utility",
  "background": {
    "page": "background.html"
  },
  "browser_action": {
    "default_icon": "gopher.png",
    "default_popup": "popup.html"
  },
  "omnibox": { "keyword": "golang" },
  "icons": {
    "16": "gopher.png"
  },
  "permissions": [
     "tabs"
  ]

See https://go.dev/wiki/Go-Release-Cycle and in particular the
[Release Maintenance](https://go.dev/wiki/Go-Release-Cycle#release-maintenance)
part of that page.

## Reporting a Vulnerability