All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Eric Wheeler <bcache@lists.ewheeler.net>
Cc: linux-bcache@vger.kernel.org
Subject: Re: [PULL] bcache: fix cache_set_flush() NULL pointer dereference on OOM
Date: Wed, 9 Mar 2016 09:23:52 -0700	[thread overview]
Message-ID: <56E04E18.1060805@kernel.dk> (raw)
In-Reply-To: <alpine.LRH.2.11.1603090330430.15354@mail.ewheeler.net>

On 03/08/2016 08:36 PM, Eric Wheeler wrote:
> On Tue, 8 Mar 2016, Jens Axboe wrote:
>
>> On 03/07/2016 04:36 PM, Eric Wheeler wrote:
>>> Hi Jens,
>>>
>>> Here is another OOM fix for bcache.  Please pull:
>>>
>>>     git pull https://bitbucket.org/ewheelerinc/linux.git
>>>     v4.5-rc7-bcache-fixes
>>>
>>>    # git diff --stat v4.5-rc7
>>>    drivers/md/bcache/super.c | 3 +++
>>>    1 file changed, 3 insertions(+)
>>
>> I pulled this and the previous, but for 4.6. They are all marked stable, so
>> that should be fine.
>>
>> Note that your 2nd patch in the -rc6 branch, this one:
>>
>> bcache: cleaned up error handling around register_cache()
>>
>> had a 4 cases of trailing white space. Please ensure that future patches are
>> cleaned up, I fixed that one up.
>
> Interesting, do you mean whitespace at the end of a line with code or
> empty lines containing whitespace or both?  Something matched by [ ]+$  ?

Both. You had both trailing white space at the end of a line, and a 
space at the start of a new line.

> Is it acceptable to have empty likes whith whitespace leading up to the
> indent level?  eg:
> 	if (1) {
> 		foo
> 		<<whitespace-to-here but line is blank
> 		bar
> 	}

Nope

-- 
Jens Axboe

      reply	other threads:[~2016-03-09 16:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-07 23:36 [PULL] bcache: fix cache_set_flush() NULL pointer dereference on OOM Eric Wheeler
2016-03-08 16:20 ` Jens Axboe
2016-03-09  3:36   ` Eric Wheeler
2016-03-09 16:23     ` Jens Axboe [this message]

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=56E04E18.1060805@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=bcache@lists.ewheeler.net \
    --cc=linux-bcache@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.