Comment # 1 on bug 1231290 from heming zhao

1.
we decide to update the drbd version from 9.1.16 to 9.1.22 to fix the build
issue.

2.
For building drbd 9.1.22, the compilation method in drbd.spec has been updated.
the relevant drbd commit is d6765fe9940e ("build,compat: do not patch git
tracked sources; apply compat patch in build subdir instead")

3.
the suse drdb.spec creates a folder 'source' and only copies rpm SOURCE folder
'.drbd_git_revision' into it. We have removed the 'source' folder from this
version update.

4.
with the default drbd-9.1.22.tar.gz plus linbit upstream patches, the source
code can be built successfully. However, there are still a few kernel APIs
issue.

  -------------------
  GENPATCHNAMES   6.11.0-1-default
  APPLIED_COCCI_FILES
queue_flag_stable_writes__no_present
disk_update_readahead__no_present
blk_queue_update_readahead__no_present
blk_queue_write_cache__no_present__yes_flush
  -------------------

the reason drbd can successfully build with imcompatbile kernel ABIs is that
the current drbd code never use all imcompatible kernel APIs.
these imcompatbile APIs only trigger the drbd coccinelle test program.

We have created a SUSE-specific patch to fix the above ABI "not present"
issues.
- boo1231290_fix_drbd_build_error_against_kernel_v6.11.0.patch

after above patch, drbd reports below APIs no_present
-------------------
GENPATCHNAMES   6.11.0-1-default
APPLIED_COCCI_FILES
queue_flag_stable_writes__no_present
disk_update_readahead__no_present
-------------------

Again: current drbd code never uses the imcompatible APIs, so the drbd can be
built successfully even if some APIs are no_present.