Date: Tue, 13 Apr 2021 15:15:17 +0200 From: Stefan Esser <se@freebsd.org> To: Konstantin Belousov <kostikbel@gmail.com> Cc: freebsd-fs@freebsd.org, Alexander Lochmann <alexander.lochmann@tu-dortmund.de> Subject: Re: [struct buf] Unlocked access to b_vflags? Message-ID: <3a3cfaa1-c240-c94b-2e2f-15ce05eaac4f@freebsd.org> In-Reply-To: <YHWQDOVcQmr6Rj8C@kib.kiev.ua> References: <792c8a3d-8ea6-073f-3fda-b3eb793ef2b9@tu-dortmund.de> <YHVxfMrU9lmw3sG9@kib.kiev.ua> <ad235e06-ec65-bd0f-e665-fde25dc35cf1@tu-dortmund.de> <YHWGnboDlRugVSsg@kib.kiev.ua> <291727c7-df2e-3fa6-ebb0-597b8deff461@tu-dortmund.de> <YHWQDOVcQmr6Rj8C@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --4LODb3wWheP8m5Gl4JKjxTFD0pc1JGlLk Content-Type: multipart/mixed; boundary="mPL7mUYRmTWZmQEESdzTYmiVh4HtvPgNC"; protected-headers="v1" From: Stefan Esser <se@freebsd.org> To: Konstantin Belousov <kostikbel@gmail.com> Cc: freebsd-fs@freebsd.org, Alexander Lochmann <alexander.lochmann@tu-dortmund.de> Message-ID: <3a3cfaa1-c240-c94b-2e2f-15ce05eaac4f@freebsd.org> Subject: Re: [struct buf] Unlocked access to b_vflags? References: <792c8a3d-8ea6-073f-3fda-b3eb793ef2b9@tu-dortmund.de> <YHVxfMrU9lmw3sG9@kib.kiev.ua> <ad235e06-ec65-bd0f-e665-fde25dc35cf1@tu-dortmund.de> <YHWGnboDlRugVSsg@kib.kiev.ua> <291727c7-df2e-3fa6-ebb0-597b8deff461@tu-dortmund.de> <YHWQDOVcQmr6Rj8C@kib.kiev.ua> In-Reply-To: <YHWQDOVcQmr6Rj8C@kib.kiev.ua> --mPL7mUYRmTWZmQEESdzTYmiVh4HtvPgNC Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: quoted-printable Am 13.04.21 um 14:35 schrieb Konstantin Belousov: > On Tue, Apr 13, 2021 at 02:13:57PM +0200, Alexander Lochmann wrote: >> "The bug was found by analyzing the memory accesses to certain data ty= pes >> and lock operations while running a load. The whole workflow is called= >> LockDoc." >> or >> "The bug was found by performing lock analysis using LockDoc." >> Is this enough, or shall I explain it in more detail? >> >> Unfortunately, we do not have a project page yet. >> I, however, have the link to our paper: >> https://doi.org/10.1145/3302424.3303948 > But it is beyond the paywall? Since I have been interested in these papers, too, I have looked for alternate download sites: https://ess.cs.tu-dortmund.de/Staff/al/Publications/files/eurosys-2019-lo= ckdoc-lochmann.pdf And a newer follow-up paper: https://dl.gi.de/bitstream/handle/20.500.12116/34350/Paper01.pdf Regards, STefan --mPL7mUYRmTWZmQEESdzTYmiVh4HtvPgNC-- --4LODb3wWheP8m5Gl4JKjxTFD0pc1JGlLk Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsB5BAABCAAjFiEEo3HqZZwL7MgrcVMTR+u171r99UQFAmB1mWUFAwAAAAAACgkQR+u171r99UT5 gwf9FhaXfbpomLnJJDruQbhw6UDgAggfVoSnJgOyj1ZXHwQLXLk+4tAz8hiONB4j8yMBiVUY70sX ufaLPy4gLOcnbc6+/CETlg+dX42M/jP3pvqyokbgqm8PoF5xRtpHmqpNxfvrp4ATEaVbM1z/6sY8 Vo4eB0iKlGNz3b3E6ZevbjNhCuilLmI6/XPZp1cpl8T0zGsmTw6r+UXsLWQ6Dmq9RMdGErl+0Xlj gcWnmJ+Vat3SxAYBCwC6Tx2UfutCwozmhdyTThbRhWjJQX4ZSRDPz8IKGv77Z+LjfCdbh1pI8LXS D56MD3Cnkh0vYCeova/5L/xwWIj5gHKUeie7me5BoQ== =AGk/ -----END PGP SIGNATURE----- --4LODb3wWheP8m5Gl4JKjxTFD0pc1JGlLk--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3a3cfaa1-c240-c94b-2e2f-15ce05eaac4f>