From: Sergei Antonov <saproj@gmail.com>
To: Hin-Tak Leung <htl10@users.sourceforge.net>
Cc: Vyacheslav Dubeyko <slava@dubeyko.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
Sasha Levin <sasha.levin@oracle.com>,
Anton Altaparmakov <aia21@cam.ac.uk>,
Al Viro <viro@zeniv.linux.org.uk>,
Christoph Hellwig <hch@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Sougata Santra <sougata@tuxera.com>
Subject: Re: [PATCH] hfsplus: release bnode pages after use, not before
Date: Mon, 8 Jun 2015 18:47:09 +0200 [thread overview]
Message-ID: <CABikg9z61CyTTaU7tbs5APD+3k-kX7knb-gm-OpTkwenS74tJg@mail.gmail.com> (raw)
In-Reply-To: <1433781680.24509.YahooMailBasic@web172301.mail.ir2.yahoo.com>
On 8 June 2015 at 18:41, Hin-Tak Leung <htl10@users.sourceforge.net> wrote:
> ------------------------------
> On Mon, Jun 8, 2015 4:45 PM BST Vyacheslav Dubeyko wrote:
>
>>On Sun, 2015-06-07 at 02:42 +0200, Sergei Antonov wrote:
>> Fix this bugreport by Sasha Levin:
>> http://lkml.org/lkml/2015/2/20/85 ("use after free")
>> Make sure mapped pages are available for the entire lifetime of hfs_bnode.
>>
>>
>>Sorry, I missed the point. What do you try to fix? How this change fixes
>>the issue?
>>
>>I think that maybe this fix makes sense. But it needs to describe it
>>more deeply. Could you describe the fix with more details?
>>
>>Thanks,
>>Vyacheslav Dubeyko.
>>
>>
>
> About this change, I also have two comments to make, one
> stylistic, one logical - you basically removed the ''#if 0",
> so I'd like to know how the "#if 0" came to be in the first place -
> I just haven't got the time to look through 'git blame' yet.
> Dead code should be removed, and that wasn't removed probably
> because it was too old i.e. already there for years.
"#if 0" has been there since the code was submitted to the kernel.
> Also there is no need to add those braces {}. I believe
> the kernel coding guideline explicitly stated not to,
> for one-statement bodies in loops?
Only for if statements (if I understand the coding style right).
next parent reply other threads:[~2015-06-08 16:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1433781680.24509.YahooMailBasic@web172301.mail.ir2.yahoo.com>
2015-06-08 16:47 ` Sergei Antonov [this message]
[not found] <1434584504.1063.YahooMailBasic@web172304.mail.ir2.yahoo.com>
2015-06-18 2:51 ` [PATCH] hfsplus: release bnode pages after use, not before Hin-Tak Leung
2015-06-18 12:58 ` Sergei Antonov
2015-06-18 15:37 ` Hin-Tak Leung
2015-06-18 16:19 ` Sergei Antonov
2015-06-18 17:16 ` Hin-Tak Leung
2015-06-18 20:51 ` Sergei Antonov
2015-06-18 22:16 ` Hin-Tak Leung
2015-06-19 1:30 ` Sergei Antonov
2015-06-07 0:42 Sergei Antonov
2015-06-08 15:45 ` Vyacheslav Dubeyko
2015-06-08 16:32 ` Sergei Antonov
2015-06-08 16:45 ` Viacheslav Dubeyko
2015-06-08 16:50 ` Sergei Antonov
2015-06-09 22:15 ` Andrew Morton
2015-06-09 23:00 ` Anton Altaparmakov
2015-06-09 23:08 ` Anton Altaparmakov
2015-06-09 23:16 ` Andrew Morton
2015-06-09 23:34 ` Anton Altaparmakov
2015-06-09 23:23 ` Anton Altaparmakov
2015-06-09 23:40 ` Sergei Antonov
2015-06-14 2:27 ` Hin-Tak Leung
2015-06-14 14:18 ` Sergei Antonov
2015-06-17 23:26 ` Hin-Tak Leung
2015-06-18 13:09 ` Sergei Antonov
2015-06-09 18:06 ` Anton Altaparmakov
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=CABikg9z61CyTTaU7tbs5APD+3k-kX7knb-gm-OpTkwenS74tJg@mail.gmail.com \
--to=saproj@gmail.com \
--cc=aia21@cam.ac.uk \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=htl10@users.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sasha.levin@oracle.com \
--cc=slava@dubeyko.com \
--cc=sougata@tuxera.com \
--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;
as well as URLs for NNTP newsgroup(s).