On Thu, Mar 11, 2021 at 01:36:26AM -0800, Li Li wrote:
> On Wed, Mar 10, 2021 at 11:33 PM Greg KH wrote:
> >
> > On Wed, Mar 10, 2021 at 02:52:49PM -0800, Li Li wrote:
> > > if (target_proc) {
> > > binder_inner_proc_lock(target_proc);
> > > + target_proc->outstandi
On Wed, Mar 10, 2021 at 11:33 PM Greg KH wrote:
>
> On Wed, Mar 10, 2021 at 02:52:49PM -0800, Li Li wrote:
> > if (target_proc) {
> > binder_inner_proc_lock(target_proc);
> > + target_proc->outstanding_txns--;
> > + WARN_ON(target_proc->outstanding_txns
On Wed, Mar 10, 2021 at 02:52:49PM -0800, Li Li wrote:
> if (target_proc) {
> binder_inner_proc_lock(target_proc);
> + target_proc->outstanding_txns--;
> + WARN_ON(target_proc->outstanding_txns < 0);
WARN_* is a huge crutch, please just handle stuff like
From: Marco Ballesio
Frozen tasks can't process binder transactions, so a way is required to
inform transmitting ends of communication failures due to the frozen
state of their receiving counterparts. Additionally, races are possible
between transitions to frozen state and binder transactions enq
