docs(bpf): update unprivileged_bpf_disabled description

[spacewander]

See https://www.suse.com/support/kb/doc/?id=000020545
Signed-off-by: spacewander spacewanderlzx@gmail.com

Please ensure your pull request adheres to the following guidelines:

• For first time contributors, read Submitting a pull request
• All code is covered by unit and/or runtime tests where feasible.
• All commits contain a well written commit description including a title,
  description and a Fixes: #XXX line if the commit addresses a particular
  GitHub issue.
• If your commit description contains a Fixes: <commit-id> tag, then
  please add the commit author[s] as reviewer[s] to this issue.
• All commits are signed off. See the section Developer’s Certificate of Origin
• Provide a title or release-note blurb suitable for the release notes.
• Thanks for contributing!

[qmonnet]

Thanks! That's a useful precision.

I've got a few observations:

• Could you please improve the title of your second commit (or alternatively, squash them)?
• I see the SUSE ticket, but better link references for the commit description would be instead:
  • https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=08389d888287c3823f80b0216766b71e17f0aba5
  • https://www.kernel.org/doc/html/v6.1/admin-guide/sysctl/kernel.html?highlight=unprivileged_bpf_disabled#unprivileged-bpf-disabled
• Please find some additional feedback inline below.

[spacewander]

Thanks! That's a useful precision.

I've got a few observations:

* Could you please improve the title of your second commit (or alternatively, squash them)?

* I see the SUSE ticket, but better link references for the commit description would be instead:
  
  * [git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=08389d888287c3823f80b0216766b71e17f0aba5](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=08389d888287c3823f80b0216766b71e17f0aba5)
  * [kernel.org/doc/html/v6.1/admin-guide/sysctl/kernel.html?highlight=unprivileged_bpf_disabled#unprivileged-bpf-disabled](https://www.kernel.org/doc/html/v6.1/admin-guide/sysctl/kernel.html?highlight=unprivileged_bpf_disabled#unprivileged-bpf-disabled)

* Please find some additional feedback inline below.

Thanks! Updated.

[qmonnet]

Looks all good, thank you!

(Please next time squash the commits when it makes no sense to keep the second separate - I did it this time.)

[spacewander]

Looks all good, thank you!

(Please next time squash the commits when it makes no sense to keep the second separate - I did it this time.)

Thanks! I will do it the next time.

BTW, we can use GitHub's "Squash and merge" button on the PR page to squash the commits automatically before merging. The Redefine GitHub extension has the ability to remove the intermediate commit message when squashing via web UI: https://github.com/refined-github/refined-github#editing-pull-requests. I recommend these because they have saved me lots of time when I maintain open source projects. 😃

[spacewander]

Just sync the master branch into this PR...
It seems this project requires the PR to be up-to-date.

[qmonnet]

BTW, we can use GitHub's "Squash and merge" button

We have it disabled on Cilium. Although the feature could be useful at times, we prefer 1) avoiding the risk of squashing by accident when we do need to keep distinct commits to understand the changes, 2) avoiding the risks of confusion for users who are not so familiar with Git and that would see their branch modified under them, 3) avoiding to put the burden of choosing between rebase or squash for the person who merges (as a consequence, the responsibility to split/squash appropriately usually falls down to the commit author).

It seems this project requires the PR to be up-to-date.

No it's fine, as long as there's no conflict you can ignore this warning.

[qmonnet]

Checkpatch and documentation workflow have passed. Travis error is #23314. This PR is only related to docs, and the reviews are in, so we're good to go.