Re: [PATCH v2 1/2] block: Add BDRV_O_NO_SHARE for blk_new_open()

2021-04-23 Thread Kevin Wolf
Am 23.04.2021 um 11:43 hat Vladimir Sementsov-Ogievskiy geschrieben: > 22.04.2021 19:43, Kevin Wolf wrote: > > Normally, blk_new_open() just shares all permissions. This was fine > > originally when permissions only protected against uses in the same > > process because no other part of the code

Re: [PATCH v2 1/2] block: Add BDRV_O_NO_SHARE for blk_new_open()

2021-04-23 Thread Vladimir Sementsov-Ogievskiy
22.04.2021 19:43, Kevin Wolf wrote: Normally, blk_new_open() just shares all permissions. This was fine originally when permissions only protected against uses in the same process because no other part of the code would actually get to access the block nodes opened with blk_new_open(). However,

Re: [PATCH v2 1/2] block: Add BDRV_O_NO_SHARE for blk_new_open()

2021-04-22 Thread Eric Blake
On 4/22/21 11:43 AM, Kevin Wolf wrote: > Normally, blk_new_open() just shares all permissions. This was fine > originally when permissions only protected against uses in the same > process because no other part of the code would actually get to access > the block nodes opened with blk_new_open().

[PATCH v2 1/2] block: Add BDRV_O_NO_SHARE for blk_new_open()

2021-04-22 Thread Kevin Wolf
Normally, blk_new_open() just shares all permissions. This was fine originally when permissions only protected against uses in the same process because no other part of the code would actually get to access the block nodes opened with blk_new_open(). However, since we use it for file locking now,