linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Qian Cai <cai@lca.pw>
To: Eric Sandeen <sandeen@sandeen.net>, hch@lst.de
Cc: axboe@kernel.dk, viro@zeniv.linux.org.uk, hare@suse.com,
	bcrl@kvack.org, linux-aio@kvack.org,
	Linux-MM <linux-mm@kvack.org>,
	jthumshirn@suse.de, linux-fsdevel@vger.kernel.org,
	Christoph Lameter <cl@linux.com>
Subject: Re: io_submit with slab free object overwritten
Date: Fri, 22 Feb 2019 16:48:42 -0500	[thread overview]
Message-ID: <e2fdd737-2a48-ecea-10b8-f90d6866df34@lca.pw> (raw)
In-Reply-To: <0a28db73-7e52-9879-276c-adc6aaf05d4d@sandeen.net>



On 2/22/19 4:42 PM, Eric Sandeen wrote:
> On 2/22/19 3:07 PM, Qian Cai wrote:
>> Reverted the commit 75374d062756 ("fs: add an iopoll method to struct
>> file_operations") fixed the problem. Christoph mentioned that the field can be
>> calculated by the offset (40 bytes).
> 
> I'm a little confused, you can't revert just that patch, right, because others
> in the iopoll series depend on it.  Is the above commit really the culprit, or do
> you mean you backed out the whole series?

No, I can revert that single commit on the top of linux-next (next-20190222)
just fine.


  reply	other threads:[~2019-02-22 21:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-22  5:40 Qian Cai
2019-02-22 15:36 ` Christopher Lameter
2019-02-22 21:07 ` Qian Cai
2019-02-22 21:42   ` Eric Sandeen
2019-02-22 21:48     ` Qian Cai [this message]
2019-02-22 21:58       ` Eric Sandeen
2019-02-22 22:06         ` Qian Cai
2019-02-22 22:25 ` Jeff Moyer
2019-02-22 22:40 ` Jens Axboe
2019-02-23  1:58   ` Qian Cai

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=e2fdd737-2a48-ecea-10b8-f90d6866df34@lca.pw \
    --to=cai@lca.pw \
    --cc=axboe@kernel.dk \
    --cc=bcrl@kvack.org \
    --cc=cl@linux.com \
    --cc=hare@suse.com \
    --cc=hch@lst.de \
    --cc=jthumshirn@suse.de \
    --cc=linux-aio@kvack.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=sandeen@sandeen.net \
    --cc=viro@zeniv.linux.org.uk \
    /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