Messages in this thread |  | | Date | Fri, 19 Jan 2024 20:34:01 +0700 | | Subject | Re: Disk write deterioration in 5.x kernel | | From | Bagas Sanjaya <> |
| |
On 1/19/24 15:55, Linux regression tracking (Thorsten Leemhuis) wrote: > On 19.01.24 07:58, Bagas Sanjaya wrote: >> [also Cc: btrfs maintainers] >> >> On Fri, Jan 19, 2024 at 09:37:50AM +0530, Gowtham wrote: >>> >>> Is there anything I can collect to debug what is the problem in the new kernel? > > From the version numbers you provided it seems you are using vendor > kernels containing patches. You thus might want to ask the vendor for > support. Most upstream developers are unlikely to help and some even > complete ignore reports using such kernels. > > You also need to try latest mainline and bisect, as Bagas already > pointed out, as that problem might be solved already and might have > nothing to do with Btrfs at all. > >> Please don't top-post, reply inline with appropriate context instead. > > Bagas, FWIW, I think telling users this is not helpful at all and maybe > counter productive; please consider to stop doing this. >
I was writing the reminder like broonie did.
> Yes, kernel development uses inline replies -- hence it's a good idea to > point that out *to developers* that submit patches et. al. > > But most people in the world uses top-posting; you and I might not like > that, but that's how it is. Telling non-developers to adjust their > behavior to our habits will often just come over as rude. It might > nevertheless be worth it. But it's best to leave that decision to the > developers that handle the report, as they have to interact way more > with the reporter that you or I will have to. >
OK, thanks!
-- An old man doll... just what I always wanted! - Clara
|  |