From: Junxiao Bi <junxiao.bi@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>,
ocfs2-devel@oss.oracle.com, linux-aio@kvack.org,
mfasheh@suse.com, linux-kernel@vger.kernel.org,
joe.jin@oracle.com, stable@vger.kernel.org
Subject: Re: [PATCH v4 1/2] aio: make kiocb->private NUll in init_sync_kiocb()
Date: Fri, 29 Jun 2012 18:17:11 +0800 [thread overview]
Message-ID: <4FED80A7.7040507@oracle.com> (raw)
In-Reply-To: <20120629092255.GB12521@dhcp-172-17-9-228.mtv.corp.google.com>
On 06/29/2012 05:22 PM, Joel Becker wrote:
> On Thu, Jun 28, 2012 at 03:39:56PM -0700, Andrew Morton wrote:
>> On Wed, 27 Jun 2012 17:09:54 +0800
>> Junxiao Bi <junxiao.bi@oracle.com> wrote:
>>
>>> Ocfs2 uses kiocb.*private as a flag of unsigned long size. In
>>> commit a11f7e6 ocfs2: serialize unaligned aio, the unaligned
>>> io flag is involved in it to serialize the unaligned aio. As
>>> *private is not initialized in init_sync_kiocb() of do_sync_write(),
>>> this unaligned io flag may be unexpectly set in an aligned dio.
>>> And this will cause OCFS2_I(inode)->ip_unaligned_aio decreased
>>> to -1 in ocfs2_dio_end_io(), thus the following unaligned dio
>>> will hang forever at ocfs2_aiodio_wait() in ocfs2_file_aio_write().
>>>
>>> Signed-off-by: Junxiao Bi <junxiao.bi@oracle.com>
>>> Cc: stable@vger.kernel.org
>>> Acked-by: Jeff Moyer <jmoyer@redhat.com>
>>> Acked-by: Joel Becker <jlbec@evilplan.org>
>>> ---
>>> include/linux/aio.h | 1 +
>>> 1 file changed, 1 insertion(+)
>>>
>>> diff --git a/include/linux/aio.h b/include/linux/aio.h
>>> index 2314ad8..b1a520e 100644
>>> --- a/include/linux/aio.h
>>> +++ b/include/linux/aio.h
>>> @@ -140,6 +140,7 @@ struct kiocb {
>>> (x)->ki_dtor = NULL; \
>>> (x)->ki_obj.tsk = tsk; \
>>> (x)->ki_user_data = 0; \
>>> + (x)->private = NULL; \
>>> } while (0)
>>>
>>> #define AIO_RING_MAGIC 0xa10a10a1
>> hm, that code is rather cruddy. Pointless macromania.
> Agreed.
>
>> If we do this:
>>
>> static inline void init_sync_kiocb(struct kiocb *kiocb, struct file *filp)
>> {
>> *kiocb = (struct kiocb) {
>> .ki_users = 1,
>> .ki_key = KIOCB_SYNC_KEY,
>> .ki_filp = filp,
>> .ki_obj.tsk = current,
>> };
>> }
>>
>> then fs/read_write.o's .text is shrunk from 9857 bytes to 9714, which
>> is rather a lot.
>>
>> But that's all rather irrelevant to your bugfix.
> I like your solution. Junxiao, if you send me that version, I'd
> be happy to take it.
Hi Joel,
Andrew had merged this patch to his tree. Do you like the second patch "
ocfs2: clear unaligned io flag when dio fails"?
> Joel
>
next prev parent reply other threads:[~2012-06-29 10:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1340788195-20623-1-git-send-email-junxiao.bi@oracle.com>
2012-06-27 9:09 ` [PATCH v4 1/2] aio: make kiocb->private NUll in init_sync_kiocb() Junxiao Bi
2012-06-28 22:39 ` Andrew Morton
2012-06-29 9:22 ` Joel Becker
2012-06-29 10:17 ` Junxiao Bi [this message]
2012-06-29 10:29 ` Andrew Morton
2012-06-29 10:48 ` Junxiao Bi
2012-06-29 10:49 ` Junxiao Bi
2012-07-04 6:13 ` Joel Becker
2012-06-27 9:09 ` [PATCH v4 2/2] ocfs2: clear unaligned io flag when dio fails Junxiao Bi
2012-07-04 7:34 ` [Ocfs2-devel] " Joel Becker
2012-07-04 7:51 ` Junxiao Bi
2012-07-05 9:22 ` Joel Becker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FED80A7.7040507@oracle.com \
--to=junxiao.bi@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=joe.jin@oracle.com \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mfasheh@suse.com \
--cc=ocfs2-devel@oss.oracle.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).