linux-kernel - Re: blkdev_issue_discard() hangs forever if the underlying storage device is removed

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAF1ivSY0NwdZTCQQ_BG5Vk8rnjiH=sS0V08ajxc8Gw5YBwD3qA@mail.gmail.com>
Date:	Mon, 29 Aug 2011 22:15:07 +0800
From:	Lin Ming <lxy@...pku.edu.cn>
To:	Lukas Czerner <lczerner@...hat.com>
Cc:	Bart Van Assche <bvanassche@....org>,
	Jens Axboe <jaxboe@...ionio.com>,
	Mike Snitzer <snitzer@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: blkdev_issue_discard() hangs forever if the underlying storage
 device is removed

On Mon, Aug 29, 2011 at 7:56 PM, Lukas Czerner <lczerner@...hat.com> wrote:
>
> Regarding the atomic operations I do not think that implicit memory
> barriers are needed here as atomic_dec_and_test() implies memory

Which implicit memory barrier you are talking about?

> barrier, atomic_set() is out of the scope of our interest (and it would
> not cause the problem like that anyway) and reordering atomic_inc()
> would not cause problem like this as well.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/