* Re: [PATCH v2] Btrfs: fix NULL pointer dereference in log_dir_items
2018-04-05 17:11 ` David Sterba
@ 2018-04-05 17:21 ` Sasha Levin
2018-04-05 19:16 ` Greg KH
1 sibling, 0 replies; 4+ messages in thread
From: Sasha Levin @ 2018-04-05 17:21 UTC (permalink / raw)
To: dsterba@suse.cz, Liu Bo, linux-btrfs@vger.kernel.org,
stable@vger.kernel.org
On Thu, Apr 05, 2018 at 07:11:14PM +0200, David Sterba wrote:
>On Thu, Apr 05, 2018 at 04:42:34PM +0000, Sasha Levin wrote:
>> Hi.
>>
>> [This is an automated email]
>>
>> This commit has been processed by the -stable helper bot and determined
>> to be a high probability candidate for -stable trees. (score: 9.9156)
>>
>> The bot has tested the following trees: v4.15.15, v4.14.32, v4.9.92, v4.4.126,
>>
>> v4.15.15: Build OK!
>> v4.14.32: Build OK!
>> v4.9.92: Build OK!
>> v4.4.126: Build OK!
>>
>> Please let us know if you'd like to have this patch included in a stable tree.
>
>Yes, in this case we expect that the Fixes: tag will let the patch flow
>to stable after it gets applied to master.
>
>The automated stable candidate patch scanning would be helpful in cases
>where the Fixes tag is not identified or we forget to add it. I don't
>mind helping to train the bot, so I'll try respond to the messages.
Just to clarify, having just the "Fixes:" tag is not necessarily an
indicator that a patch should go into -stable.
For example, if I fix up documentation and add a Fixes: tag to point to
the commit that added the original documentation, it's not -stable
material since we don't take documentation patches. Or, if the patch
that the new commit fixes didn't make it into any releases, it's not
stable material either.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH v2] Btrfs: fix NULL pointer dereference in log_dir_items
2018-04-05 17:11 ` David Sterba
2018-04-05 17:21 ` Sasha Levin
@ 2018-04-05 19:16 ` Greg KH
1 sibling, 0 replies; 4+ messages in thread
From: Greg KH @ 2018-04-05 19:16 UTC (permalink / raw)
To: dsterba, Sasha Levin, Liu Bo, linux-btrfs@vger.kernel.org,
stable@vger.kernel.org
On Thu, Apr 05, 2018 at 07:11:14PM +0200, David Sterba wrote:
> On Thu, Apr 05, 2018 at 04:42:34PM +0000, Sasha Levin wrote:
> > Hi.
> >
> > [This is an automated email]
> >
> > This commit has been processed by the -stable helper bot and determined
> > to be a high probability candidate for -stable trees. (score: 9.9156)
> >
> > The bot has tested the following trees: v4.15.15, v4.14.32, v4.9.92, v4.4.126,
> >
> > v4.15.15: Build OK!
> > v4.14.32: Build OK!
> > v4.9.92: Build OK!
> > v4.4.126: Build OK!
> >
> > Please let us know if you'd like to have this patch included in a stable tree.
>
> Yes, in this case we expect that the Fixes: tag will let the patch flow
> to stable after it gets applied to master.
Fixes: tags almost never cause that to happen, unless I am bored and go
digging for them.
Please read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how to do this properly if you want a patch applied to the stable
tree.
thanks,
greg k-h
^ permalink raw reply [flat|nested] 4+ messages in thread