Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1502420
| From | Jeff Moyer <jmoyer@redhat.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] aio: fix a use after free (and fix freeze protection of aio writes) |
| Date | 2016-10-17 22:10 +0200 |
| Message-ID | <stmop-8jb-17@gated-at.bofh.it> (permalink) |
| References | <ssMEh-1F5-1@gated-at.bofh.it> <stkPD-7cX-19@gated-at.bofh.it> <stliG-7os-27@gated-at.bofh.it> <stm54-7V9-37@gated-at.bofh.it> <stmeK-7YZ-19@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Peter Zijlstra <peterz@infradead.org> writes:
> On Mon, Oct 17, 2016 at 03:40:24PM -0400, Jeff Moyer wrote:
>> Christoph Hellwig <hch@lst.de> writes:
>>
>> > On Mon, Oct 17, 2016 at 02:19:47PM -0400, Jeff Moyer wrote:
>> >> This ends up being a call to __sb_end_write:
>> >>
>> >> void __sb_end_write(struct super_block *sb, int level)
>> >> {
>> >> percpu_up_read(sb->s_writers.rw_sem + level-1);
>> >> }
>> >>
>> >> Nothing guarantees that submission and completion happen on the same
>> >> CPU. Is this safe?
>> >
>> > Good point. From my reading of the percpu_rwsem implementation it
>> > is not safe to release it from a different CPU. Which makes me
>> > wonder how we can protect aio writes properly here..
>>
>> Could we just change percpu_rw_semaphore->read_count to be a signed
>> integer? The down_write path sums up the counters from all cpus...
>
> To what point?
Duh, nevermind. You're right, it should work as-is.
-Jeff
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH] aio: fix a use after free (and fix freeze protection of aio writes) Christoph Hellwig <hch@lst.de> - 2016-10-16 08:00 +0200
Re: [PATCH] aio: fix a use after free (and fix freeze protection of aio writes) Jeff Moyer <jmoyer@redhat.com> - 2016-10-17 20:30 +0200
Re: [PATCH] aio: fix a use after free (and fix freeze protection of aio writes) Christoph Hellwig <hch@lst.de> - 2016-10-17 21:00 +0200
Re: [PATCH] aio: fix a use after free (and fix freeze protection of aio writes) Jeff Moyer <jmoyer@redhat.com> - 2016-10-17 21:50 +0200
Re: [PATCH] aio: fix a use after free (and fix freeze protection of aio writes) Peter Zijlstra <peterz@infradead.org> - 2016-10-17 22:00 +0200
Re: [PATCH] aio: fix a use after free (and fix freeze protection of aio writes) Christoph Hellwig <hch@lst.de> - 2016-10-17 22:10 +0200
Re: [PATCH] aio: fix a use after free (and fix freeze protection of aio writes) Jeff Moyer <jmoyer@redhat.com> - 2016-10-17 22:10 +0200
Re: [PATCH] aio: fix a use after free (and fix freeze protection of aio writes) Peter Zijlstra <peterz@infradead.org> - 2016-10-17 22:00 +0200
Re: [PATCH] aio: fix a use after free (and fix freeze protection of aio writes) Jeff Moyer <jmoyer@redhat.com> - 2016-10-17 22:10 +0200
Re: [PATCH] aio: fix a use after free (and fix freeze protection of aio writes) Christoph Hellwig <hch@lst.de> - 2016-10-24 08:40 +0200
csiph-web